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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by clarifying that claimable_only=true returns only currently funded, open-to-solve work. It does not contradict the annotations and provides enough extra context for a safe read operation.

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?

The description is two sentences, front-loads the primary use case, and provides the key filter directive without extraneous detail. Every clause 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?

With zero required parameters, a complete output schema, and annotations covering safety and idempotency, the description provides the remaining essential context: why to use the tool and how to filter for funded open work. Nothing critical is missing for an agent to invoke 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%, so the schema fully documents both parameters. The description restates the claimable_only behavior but adds no new semantic detail beyond the schema. It earns the baseline score for not going below zero-guidance, but does not meaningfully enhance the parameter understanding.

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 title 'List canonical bounties' and the description make the resource and action clear: list bounties and optionally filter to claimable ones. The phrase 'canonical lifecycle inventory' adds specificity but is somewhat jargon-heavy, and it does not explicitly distinguish this tool from similar siblings like get_bounty_feed.

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?

The description states when to use the tool: when the person wants funded Agent Bounties work or canonical lifecycle inventory. It also gives a concrete directive for the claimable_only parameter. However, it does not mention any alternatives or when not to use it, so it stops short of full routing guidance.

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