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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lowered, yet the description adds real non-obvious context: it returns a first-party continuation URL and warns against treating an empty index as a failed transaction or restarting payment. The terms are somewhat cryptic (what 'empty index' refers to is unexplained), keeping it from a 5.

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 the purpose front-loaded and no filler. The caution clause is dense but earns its place; some phrasing is oblique rather than verbose.

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, the description does state the key return value (the existing continuation URL) and the safety profile is covered by annotations. What 'posting progress' concretely contains remains unspecified, so it is not fully complete.

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% and each parameter is richly documented in the schema (wallet, protocol gating, operation_id session requirement, bounty_contract). The description adds no parameter-level syntax or format detail, so the baseline 3 applies.

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 (Read) and resource (canonical posting progress and gas sponsorship) and notes the returned continuation URL, so an agent knows what it retrieves. It does not explicitly distinguish itself from close siblings like get_bounty_action_status, so it stops short of a 5.

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?

There is no statement of when to call this versus the many sibling status/read tools (get_bounty_action_status, get_posting_options, etc.). The warnings about not inferring failure or restarting payment are behavioral cautions, not usage routing.

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