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

The description discloses the full behavioral impact: real money moves into escrow, approval must be OFF, the funder never wins, and the judging/payment process is automated. It goes far beyond the minimal annotations (readOnlyHint=false, destructiveHint=false) by explaining exactly what side effects occur and what the returned fund_sig represents.

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?

The description is detailed but well-structured: prerequisites first, then the action, then outcomes and constraints. Each sentence adds necessary context for a tool that moves real money. Slightly longer than ideal, but the density justifies the length.

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 the tool's complexity (5 params, no output schema, real-money implications), the description covers all necessary context: prerequisites, side effects, constraints, auth, and the returned receipt. An agent has everything it needs to call this tool correctly.

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 coverage is 100%, so each parameter is already documented in the schema. The description adds contextual value by explaining how pot_usdc and deadline_minutes relate to the escrow and judging process, but it does not introduce new parameter semantics beyond what the schema provides. Baseline 3 is 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?

The description clearly states the action: 'Post a bounty on the board' with real USDC, and distinguishes it from siblings like bounty_list and bounty_submit. It specifies the resource (playground bounties) and the verb (create/escrow), leaving no ambiguity about what the tool does.

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?

It provides explicit step-by-step prerequisites: first grant a USDC mandate via signet_grant with specific scoping, then call this tool. It also states constraints (pot size, deadline ranges, max open per account) and the auth requirement, giving clear when-to-use context without needing to consult alternatives.

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