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

Annotations already establish readOnly/destructive=false/openWorld=false, and the description adds real value beyond them: it discloses that the call requires a locally signed proof (auth requirement) and clarifies lifecycle semantics ('Owner acceptance remains unpaid; payout is owner-run and off'). That off-platform payout note is non-obvious and prevents wrong assumptions.

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 compact sentences, front-loaded with the core action and auth mode. The payout sentence is tangential to invocation but short and informative, so little is wasted.

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 read-only, auth-gated tool with no output schema, the description covers the auth mode and payout semantics but omits what the status response contains and how the five signing parameters relate. Adequate but leaves real gaps an agent would face at call time.

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% across 5 required params, so the description carries the full burden, and it largely does not meet it. The phrase 'locally signed GET ... proof' hints that did/nonce/timestamp/signature form a signed auth envelope, but it never explains how to construct or order those values, and says nothing about bounty_id usage.

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: reading bounty status, and distinguishes two audience views (claimant vs posting operator). It is separable from siblings like voidly_bounties and voidly_bounty_claim, though the phrase 'claimant or posting operator view' could be sharper about which status fields are returned.

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 when-to-use or when-not guidance relative to siblings such as voidly_bounties, voidly_bounty_claim, or voidly_bounty_submit. The claimant/operator framing implies an audience but does not tell an agent which tool to pick in a given situation.

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