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

With no annotations present, the description carries the full disclosure burden, and it does useful work: it declares the tool is free (no x402 challenge) and that its content is deterministic and pinned, which are behavioral facts not otherwise available. However, it says nothing about the response shape or size — whether the criteria come back as JSON, markdown, or a blob — so an agent cannot anticipate what it will receive.

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?

The content enumeration is front-loaded in the first sentence and the actionable instruction ('read these before paying') plus the free-call note follow immediately. The list of internal artifacts (R1-R9, never-a-repair, corpus identity) is dense jargon but each item identifies real content; only the HTTP-equivalent URL is arguably filler.

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 zero-parameter reference-retrieval tool with no output schema, the description covers what the document contains, why to read it, and that it costs nothing. The only real gap is the return format, which matters because there is no output schema to fall back on.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the schema is empty and coverage is fully satisfied by construction. Baseline 4 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 resource ('The published criteria for the Argument Check service (tool-argument/v1)') and enumerates its contents: schema subset, R1-R9 repair whitelist, never-a-repair list, and test corpus identity. That is far more specific than a tautology and lets an agent infer it is a static reference document rather than the check itself, though it never names argument_check_check or argument_check_precheck as the tools this document governs.

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?

'Read these before paying - every verdict is reproducible from them' gives a clear triggering condition (consult before invoking the paid check) and explains why (reproducibility). It also says the call itself is free. It stops short of explicitly stating when NOT to use it or naming the sibling tools that consume these criteria.

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