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

Annotations declare non-read-only, non-destructive, open-world, so the safety profile is partly covered. The description still adds real behavioral value beyond them: the work is sent back to the worker, a fresh deadline is issued, and critically the escrow is unaffected, which is non-obvious state information for a mutation 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 tight sentences with no waste: the trigger condition comes first, then the effect. Every clause carries information.

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 three-parameter mutation with no output schema, the description covers the essential outcome (work returned, new deadline, escrow unchanged). It omits edge cases such as revision limits or whether the previous deadline is superseded, but nothing an agent needs to invoke it correctly 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%, so the schema already documents bounty_id, note, and hours (including the default-to-bounty-timeframe behavior). The description restates note and deadline semantics but adds no syntax or constraints beyond the schema, making baseline 3 appropriate.

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 and resource: sends submitted work back to the worker with a note and new deadline. The 'needs fixing' framing implicitly contrasts with approve_work, though it never names the sibling, so an agent must infer the pairing.

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 a clear triggering condition ('when submitted work on the user's bounty needs fixing'), which is enough context to select it over approve_work. It stops short of explicitly naming the alternative or stating when not to use it.

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