list_task_bounties

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

No annotations exist, so the description carries full behavioral burden. It usefully discloses that the call is free ($0.0000 USDC) and gives the default status/limit, but says nothing about permissions, rate limits, pagination, or the shape of returned results.

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?

Purpose and cost are front-loaded, but the 'Keywords:' line restates the description nearly verbatim and adds no decision-relevant information. The Args block is helpful; the keyword stuffing is filler.

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 two-parameter, no-required-input list tool with no output schema, the description covers filtering and defaults adequately. It leaves the return format and result size/ordering undocumented, which an agent listing bounties would want.

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%, so the description must compensate, and it does: it enumerates the four valid status values ('OPEN','CLAIMED','VERIFIED','RELEASED') and the default, plus the default limit. It omits the limit's range/behavior, so it is strong but not complete.

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 ('Discover active task bounties') and adds scope ('without prior out-of-band IDs'), which implicitly separates it from get_task_escrow_status and claim_task_bounty. It does not explicitly name a sibling, so differentiation is inferred rather than stated.

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 clear context: autonomous worker agents browsing open tasks/bounties without needing known IDs. This is exactly the discovery entry point ahead of claim_task_bounty. No explicit when-not conditions or named alternatives are provided, keeping it below a 5.

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