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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is fully covered. The description adds only that results cover 'delivery and run' statistics, without saying whether stats are live or lagged, whether an unsent campaign returns empty, or what happens for an invalid id — a modest value-add.

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?

One short, front-loaded sentence with no filler. It is efficient but borders on under-specified rather than deliberately tight.

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 simple one-parameter read tool with a fully documented schema and safety annotations, this is minimally sufficient. With no output schema, though, an agent gets no hint about what the statistics contain (counts, rates, time windows), leaving return-value expectations entirely unknown.

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 coverage is 100% and the single campaign_id parameter is documented there with length constraints and provenance. The description adds nothing about the parameter, which is acceptable given the schema does the work, but earns only the baseline.

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?

States a specific resource (one campaign) and content (delivery and run statistics), which is more informative than a bare 'get stats'. However, it does not distinguish itself from nearby stats-oriented siblings such as spur_get_property_stats or spur_get_direct_mail_analytics, so an agent must infer the boundaries.

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 statement of when to use this tool versus list_campaigns, get_direct_mail_analytics, or other reporting tools, and no prerequisites (e.g., campaign must have been sent). The only routing cue, 'UUID from a Spur list/search tool', lives in the parameter schema, not the description.

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