Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive behavior. The description adds useful behavioral detail beyond that: entries are returned newest first and each carries workflow name, node label, status, and payload, with concrete examples of readable content. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no filler; the core function and ordering are front-loaded, the payload detail earns its place, and the sibling comparison is packed into the final sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only history tool with no output schema, the description covers the key return contents and ordering. It stops short of explaining optional parameters like leadSource and workspaceId or pagination behavior, but the core invocation path (required leadId) is clear enough that an agent can call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description needed to explain parameter roles, but it only alludes to 'one lead' and 'this workspace' without mapping to leadId, leadSource, workspaceId, or limit. The schema's types/defaults are visible, but the description adds almost no parameter-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get everything this workspace has done to one lead, across every workflow and campaign, newest first.' It also explicitly differentiates from campaignstack_get_node_activity, so an agent can tell them apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: 'Use this instead of campaignstack_get_node_activity when the question is about a person rather than about one node,' and explains why node activity is insufficient ('a lead waiting at a later step looks untouched there'). This is clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.