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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces the read-only profile and adds context beyond annotations: the tool returns structured data and does not render UI ('without rendering another widget'). 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?

Two sentences with zero filler; the purpose and primary routing decision are front-loaded before the secondary read-only clarification. Every sentence 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 read-only fetch with rich annotations, an output schema, and all-optional parameters, the description covers purpose, usage context, and sibling routing. The main gap is that parameter semantics are left entirely to the schema, whose enums partially compensate; return values need not be explained because an output schema exists.

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 description coverage is 0% across 6 parameters, but the description mentions none of them (view, limit, network, work_state, source_type, payment_state) and gives no guidance on filtering or defaults. The enum values in the schema are partially self-describing, which prevents a score of 1, but the description fails to compensate for the coverage gap.

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 pair: fetch 'fresh structured bounty data' for the model or mounted feed. Explicitly contrasts with render_bounty_feed, making the distinction from the most confusable sibling unambiguous.

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 when-to-use condition ('when the model or mounted feed needs fresh structured bounty data without rendering another widget') and names the alternative with its selection criterion ('use render_bounty_feed only when the person wants the interactive feed shown'). No inference required.

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