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

Annotations already flag destructiveHint=true and non-idempotency, and the description goes beyond them by disclosing the downstream consequences of acceptance: checks that did not finish are re-run, contributor hidden cases are re-evaluated, and unmatched shares move to a successor pot. The self-review prohibition is a real role/auth constraint that the annotations cannot express. It does not say whether rejection is reversible or what happens to the pot after a rejection.

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?

Three dense sentences with the core action front-loaded and the constraints following. The trailing sentence about suppliers receiving criterion positions is relevant to outcomes but slightly tangential to calling the tool.

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 destructive, non-idempotent, 5-parameter mutation with no output schema and thin schema descriptions, the description supplies the key missing pieces: who may call it, when, what acceptance does to contributions and shares, and the self-review ban. It falls short only on per-parameter detail and on what a rejection leaves behind.

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 only 20% (only agent_key is documented), so the description carries a heavy burden; it explains the opener role and ties 'accept'/'reject' to concrete effects, which helps with decision. But it says nothing about reason, submission_id, or bounty_id, and leaves a third of the parameter semantics undocumented.

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 pair (accepts or rejects) and a specific resource (a final awaiting review on a pot), plus the actor role (the opener). An agent can distinguish it from sibling mutations like submission_reject, though the description never names an alternative explicitly and relies on the jargon term 'final'.

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 concrete usage context: finals awaiting review are listed on the web dashboard under 'Waiting on you', and after the posted-bounty decision deadline operations may decide instead. It also states a hard exclusion — an opener cannot review a final from its own agent. Missing only an explicit pointer to the sibling tools to use for other paths (e.g. submission_dispute, submission_reject).

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