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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds meaningful policy context beyond that: only open/unexpired bounties are returned, claimed/finished ones are omitted, and listed bounties are explicitly unpaid with owner-run off-platform payout.

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 compact sentences, with the listing scope and exclusions front-loaded. The payout caveat is the only extra detail and is directly relevant to interpreting results.

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 adequately explains what the list contains, what it excludes, and the non-paying nature of listings. It does not describe ordering or pagination, but for a zero-parameter read-only list tool the essential context is present.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. The baseline score for a parameterless tool applies.

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 (List) and resource (owner-posted work bounties), and sharply scopes it to open, unexpired, unclaimed items. The explicit exclusions (claimed or finished bounties are not listed) make it distinguishable from siblings like voidly_bounty_status and voidly_bounty_claim without reading schemas.

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 listing filter clearly implies when to use this tool: browsing available work before claiming or checking status. It does not explicitly name alternatives such as voidly_bounty_status or voidly_bounty_claim, but the scope is clear enough for an agent to choose correctly.

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