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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds that these are network-needed capabilities with a reward mechanism, which is useful framing, but says nothing about pagination, return shape, or whether the 'open' wording means results are pre-filtered despite the status enum offering other values.

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 tight sentences with the core purpose front-loaded and no filler. Both sentences earn their place, though the second is more motivational than operational.

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 simple read-only list tool with full schema coverage and no output schema, the description covers what the tool returns conceptually and who uses it. The only gap is the ambiguity between 'open bounties' in prose and the multi-value status filter, but nothing critical for a correct invocation is missing.

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 100% with a documented status enum and capabilityType field, so the schema carries the parameter burden and baseline 3 applies. The description adds no filter syntax or defaulting behavior beyond what the schema already states.

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 and resource ('List open bounties for capabilities the network needs') and adds a one-line purpose. It is clearly distinguishable from write siblings like claim_bounty or verify_bounty, but it does not name any sibling explicitly.

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?

'Operators can claim these to earn rewards by onboarding new capabilities' implies the audience and why someone looks at this list, but it never says when to call this versus claim_bounty, verify_bounty, or get_bounty_leaderboard. Usage is inferred rather than stated.

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