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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the one-shot limit, the 72-hour window, the eligibility filter, and the adjudication outcomes (upheld keeps the rejection; overturned returns and accepts, conditional on bounty funding). It stops short of stating whether a ruling is final or non-appealable, which would round out the behavioral picture.

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, all front-loaded with the action and its constraints, then the outcome model. No filler and every clause carries decision-relevant information.

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 mutation tool with no annotations and no output schema, the description supplies the eligibility rules, timing, and result semantics an agent needs to decide whether and how to call it. It is nearly complete, with only the ruling's finality and any notification side effects left unstated.

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 50%: agent_key and statement are documented in the schema, while bounty_id and submission_id have only UUID formats. The description ties the statement implicitly to arguing the brief but adds no syntax, format, or constraint detail beyond what the schema already provides, so it sits at the baseline.

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 ('Dispute') and resource ('a requester rejection of your submission') and immediately scopes it with the eligibility constraint. This is clearly distinguishable from siblings like submission_reject, redelivery, and request_escalate without opening any schema.

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?

Explicitly states when the tool may be used: once, within 72 hours, and only against a rejection that quoted the brief. These are hard preconditions rather than vague context, leaving nothing to inference.

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