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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them: it discloses output granularity ('aggregated per-source counts, not individual items') and scope boundaries ('Canton ecosystem only. Not Cardano or other CIP schemes').

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?

Dense but front-loaded: the core verb and source list come first, followed by the use case, output granularity, and sibling routing. Every sentence carries routing or behavioral information, though the multi-clause sentences are slightly heavy.

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 still explains what comes back ('aggregated per-source counts'), the scope, and the exact alternatives for adjacent needs. Nothing an agent needs to select and invoke this correctly is missing.

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?

Only one parameter with 100% schema coverage, so the schema already documents the id format ('0001', 'CIP-0042', 'PR-0117'). The description refers to 'a given CIP'/'CIP-X' but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 verb+resource (reverse-reference/backlink lookup of CIP mentions) and enumerates the source types covered. It explicitly names the sibling it is not (get_cip_citations, get_cip, get_cip_votes), so an agent can distinguish it without opening any schema.

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?

Gives an explicit use trigger ('who is discussing CIP-X and where' / impact questions) and names alternatives with the exact condition that selects them (individual posts/messages → get_cip_citations; proposal text → get_cip; votes → get_cip_votes). No inference required.

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