List bounties

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

With no annotations, the description should fully disclose behavior. It states it lists bounties with default OPEN, but omits details like read-only nature, pagination, or any side effects. The mention of 'Claim one' is misleading as it suggests an action not performed by this tool.

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, but the third clause ('Claim one...') is extraneous and not directly relevant to the tool's function. The structure is acceptable but not optimal; it could be more focused.

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?

Given no annotations, no output schema, and 4 parameters, the description is insufficient. It lacks details on return format, pagination (cursor), and full parameter usage. The tool's purpose is clear but the description is not complete enough for an agent to use it correctly without additional context.

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 low (25%, only for 'state'). The description adds value by stating the default for 'state' (OPEN), but does not explain 'sort', 'limit', or 'cursor'. It partially compensates for the schema 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?

The description clearly identifies the tool as listing bounties with a default state of OPEN. It distinguishes from sibling tools like claim or deliver by focusing on browsing. However, it mentions 'Claim one' which is not part of this tool's function, causing slight ambiguity.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for browsing, but does not mention when not to use it or provide references to other tools like synthnet_claim_bounty.

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