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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is fully covered. The description adds that results include status and recipient progress, giving a hint of the payload, but says nothing about ordering, total counts, or that offset/limit paging applies — with no output schema, more return-shape detail would have been valuable.

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?

A single tight sentence front-loads the resource with zero filler. It loses a point only because the fragment omits the operative verb, slightly reducing upfront clarity.

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?

With no output schema, the description carries the burden of describing returns and only gestures at it ('status and recipient progress'). For a paginated list tool, the absence of any paging or ordering context leaves the definition minimally viable.

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?

Schema description coverage is 100%, so limit, offset, and the status enum are fully documented in the schema. The description adds nothing about them, and its use of 'status' as a returned field rather than the filter parameter could momentarily blur the distinction between the output and the status input.

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 names the resource (the user's campaigns) and enumerates the campaign types covered (bulk email, SMS, direct mail, outreach), but it is a bare noun phrase with no verb and no differentiation from siblings like spur_get_campaign_stats. An agent can infer it is a listing operation from the name and title, but the description itself never says 'list' or 'returns a list'.

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?

There is no guidance on when to use this versus spur_get_campaign_stats, spur_list_sms_conversations, or other list endpoints, and no mention of the default page size or that results are paged. Usage is only implied by the tool name.

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