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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial beyond-schema context: per-source granularity (individual posts and messages, not just counts), full mailing-list scope with no exclusions, and the CCPEDIA-unique mailing_messages.cip_id join. It also discloses corpus scope (Canton/Daml/Splice only).

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?

Front-loaded with the core purpose and benefit, and the source enumeration is dense but useful. It runs long and has minor repetition of the CCPEDIA value proposition, but every sentence largely earns its place.

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-param, annotation-covered read tool with no output schema, the description fully conveys what is returned (per-source counts and samples) and where it draws from, leaving nothing an agent needs in order to 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?

Schema coverage is 100% and the single cip_id param already documents accepted formats (padded/unpadded, PR-xxxx). The description adds little param-specific detail beyond the ecosystem/ID requirement, so the 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 ('comprehensive citation graph for a CIP') and precisely enumerates what it covers across sources (sibling CIPs, forum posts, mailing-list messages, GitHub, blog, YouTube). It cleanly distinguishes itself from get_cip, get_cip_votes, and get_cip_mentions by naming their distinct scopes.

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?

Explicitly states when to use it ('who is referencing CIP-X and where', impact analysis, with a known CIP id), and routes to alternatives: get_cip for proposal text, get_cip_votes for votes, get_cip_mentions for legacy counts, full_context for free-text with no known id. Exclusions are clearly stated.

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