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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the redundant 'It is read-only' adds little. However, the description contributes a genuine behavioral trait beyond annotations: it does not render a widget, which is exactly the side-effect distinction an agent needs to choose between the two feed tools.

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, zero filler, and the usage condition is front-loaded before the alternative. 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 an output schema present, return values need not be explained, and the rich annotations cover the safety profile. The description covers routing and the non-rendering behavior well, but for a tool with six filter parameters it leaves parameter meaning entirely unaddressed, which is the one remaining gap.

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?

Six optional filter parameters with 0% schema description coverage, and the description says nothing about any of them (view, limit, network, work_state, source_type, payment_state). The enum values carry some self-evident meaning, but the description adds no defaults, no combination behavior, and no filter semantics, leaving the schema's bare enums to do all the work.

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 conveys that this retrieves fresh structured bounty data without rendering UI, and it explicitly distinguishes itself from the render_bounty_feed sibling. The verb is implicit rather than stated ('get' is only in the name), but the resource and the contrast with the render tool make its role identifiable.

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 an explicit when ('when the model or mounted feed needs fresh structured bounty data'), an implicit when-not, and names the alternative with the exact condition that selects it ('use render_bounty_feed only when the person wants the interactive feed shown'). Routing is fully determined.

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