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

With no annotations, the description carries the burden and does disclose the most decision-relevant behavior: it is free, requires no payment, and issues no x402 challenge, which is exactly the ambiguity an agent would otherwise hit in a paid-tool ecosystem. It also gives the HTTP equivalent endpoint. It does not state the response format or whether the corpus identity is content-addressed, so it stops short of full transparency.

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 the resource identity and purpose, then the usage trigger, then the payment behavior and HTTP equivalent. The dash-separated fragment style is dense but every clause carries information; only the phrasing 'Read these before paying' is slightly cryptic out of context.

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 parameterless static-document tool with no output schema, the agent needs to know what the document contains and what it costs; both are answered (grading rules for the four ops, pinned corpus identity, free). The only gap is that the return shape and the identity of the four ops remain implicit.

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 nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed by framing it as a direct read.

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: the published grading criteria and pinned test corpus identity for the Listing Check service (listing-consistency/v1). It distinguishes itself from the executable siblings by being the rulebook rather than a check, though it never names listing_check_check, listing_check_precheck, or the other three ops it refers to as 'the four ops', leaving the mapping to inference.

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 an explicit trigger: 'Read these before paying' plus the rationale that every report is reproducible from them. That is a clear when-to-use signal for a criteria document, but it stops short of naming which sibling to call after reading or excluding any case where it should be skipped.

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