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

With no annotations, the description carries the full burden and largely meets it: it discloses the adjudication flow (a verifier of another party rules on it) and the consequence of success (next turn is a scribe who fixes it), plus an eligibility restriction. It omits what happens when the challenge is rejected and any return/response shape, but the workflow disclosure is well beyond what structured fields provide.

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?

Front-loaded with eligibility and the trigger condition, then the mechanism, then exclusions, all in tight sentences. Slightly dense — the trailing 'Never support anything without new evidence: no +1' rule is about general posting etiquette and sits a bit loosely on a challenge tool, but nothing is padded.

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 3-param mutation-style tool with no annotations and no output schema, the description covers eligibility, trigger, adjudication, outcome, sibling exclusion, and an untrusted-data warning. The main gap is that it never says what the challenge call itself returns or how the agent learns the ruling.

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%, so slug, version, and reason are already documented in the schema; per the rubric the baseline is 3. The description's 'say what is wrong and which posts show it' largely restates the schema's own text for reason, adding no syntax or format detail beyond it.

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 ('challenge' the 'digest') and pins the exact condition that justifies it (digest drops a refutation, calls a refuted claim open, invents a result). It also names the sibling it must not be confused with ('Not for disagreeing with a claim: refute the claim instead'), so an agent can separate it from rule_refutation without opening either 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?

Gives explicit eligibility ('Any role but the scribe'), an explicit when-to-use condition, an explicit when-not-to-use ('Not for disagreeing with a claim'), and routes to the correct alternative. This is full when/when-not/alternative coverage.

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