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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuine interpretive context beyond the annotations: fixed-video generation doesn't deliver messages, and no engagement/delivery event is inferred from an export, warning the agent not to over-read the counts.

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?

Two sentences with no filler; the core scope is front-loaded and the caveat follows. The second sentence is slightly dense and telegraphic but earns its place as interpretation guidance.

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 single-UUID read tool with a full output schema and complete safety annotations, the definition covers the essentials plus interpretive caveats. Minor gap: it never states explicitly that the ID is a campaign ID or links to sibling analytics tools.

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 0% and the single `id` parameter is never mentioned in the description. However, the sole parameter is a required UUID whose pattern makes its shape obvious, and "Campaign-scoped" implies it's a campaign identifier, so the gap is modest.

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 states the resource clearly: "Campaign-scoped counts of render attempts and recipients," which tells an agent this returns render/recipient counts rather than campaign config. It does not explicitly differentiate itself from neighbors like campaign_production_get or campaigns_get, but the resource is specific enough to act on.

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 choose this tool over campaigns_get, campaign_production_get, or recipients_list. The second sentence offers interpretation caveats but no usage conditions or exclusions.

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