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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's real added value is defining what counts as a 'gap' (zero replies, no label assigned) and the Canton-specific scoping, but it says nothing about ordering, recency windows, or how the three categories are combined in the response.

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?

Three tight sentences: the gap taxonomy first, scope next, the alternative last. No filler and nothing redundant with the annotations.

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 does the work of telling the agent what the result represents, and it does so for all three gap types. Minor gaps remain around result ordering and whether categories are merged or separated.

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?

One parameter with 100% schema description coverage, so the schema already documents limit, its 1-20 range and default. The description's phrase 'max rows per gap type' restates the schema rather than adding interpretation, which is the baseline case.

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?

Specific verb ('surface') plus a precisely enumerated resource: unanswered high-view forum threads, unreplied mailing threads, and unlabeled Dev Fund proposals. The three gap categories are defined inline, so an agent knows exactly what comes back without opening the 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?

Explicitly routes a competing question away with 'For per-category funding levels use get_funding_landscape,' and gives a use framing ('where the ecosystem needs help'). It does not state a when-not condition or name the sibling list_proposals_needing_champion, which overlaps the Dev Fund gap category.

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