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

Annotations already declare the tool read-only and idempotent; the description adds meaningful context beyond that: per-source counts and samples, per-message granularity through the parsed mailing_messages.cip_id column, explicit inclusion of all lists.sync.global groups, and a Canton/Daml/Splice ecosystem restriction. No contradiction with annotations.

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?

Despite its length, every sentence earns its place: it front-loads the core output, itemizes sources, highlights the unique value proposition, then delivers clear routing to alternatives. The structure is dense yet scannable, which is appropriate for a tool with this much behavior to describe.

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 compensates by specifying exactly what will be returned (counts and samples per source), listing all source types, and adding unique-value and ecosystem-scope context. It also covers the key decision of when to use this tool versus its siblings, making it complete for an agent to invoke 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?

The input schema already fully documents cip_id with examples ('CIP-0056', '0056', 'PR-0117') and padding rules. The description adds the precondition that a known CIP id is required, but it doesn't introduce any new parameter-level semantics beyond what the schema provides, so the baseline of 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?

The description states a specific verb ('returns'), a clear resource ('citation graph for a CIP'), and enumerates every source category covered, from sibling CIPs to YouTube transcripts. It also explicitly names sibling alternatives, making the tool's unique role immediately apparent.

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?

It gives explicit when-to-use guidance: impact analysis when a specific CIP id is already known. It then names alternatives and their conditions: get_cip for proposal text, get_cip_votes for votes, get_cip_mentions for legacy aggregated counts, and full_context for free-text topics without a known CIP id.

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