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

Annotations declare the write/open-world/non-idempotent profile, and the description adds real lifecycle detail beyond that: objective pre-checks run immediately, then a human review against acceptance criteria, and payout is released only after verification. It stops short of stating what happens on failed verification or whether resubmission is allowed.

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 dense sentences with the core submission action front-loaded and the verification nuance trailing. No filler, though the parenthetical about payout is slightly buried at the end.

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 and six parameters, the description conveys the submit-and-review lifecycle adequately for an agent to call the tool. It leaves gaps on return behavior (what the pre-check result looks like) and failure/resubmission semantics, which matter for a non-idempotent write.

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 the baseline is 3, but the description adds genuine meaning for payout_address (required, Base chain, ANANSI sent there only after verification), which is not conveyed by the schema description alone. Other parameters (links, notes, api_key) get no extra narrative, so it's above baseline but not comprehensive.

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?

Specific verb+resource ('submit proof for your bounty claim') with clearly named inputs, so an agent can distinguish it from siblings like claim_bounty, release_bounty, and bounty_status. It doesn't explicitly name those siblings, but the action is unambiguous.

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 description implies the workflow context (submitting after a claim exists, followed by automated pre-checks and Haven team review), which is useful sequencing. However, it never explicitly states when to prefer this tool over claim_bounty or release_bounty, or any prerequisites such as having an existing claim.

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