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

With no annotations at all, the description carries the full disclosure burden, and it does cover the highest-risk unknown in this toolset: the call is free, has no x402 challenge, and needs no payment, plus an HTTP equivalent is given. It stops short of describing the response shape (JSON vs prose, size, section structure), so an agent knows the cost profile but not what it will actually 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 resource identity and the 'read before paying' instruction are front-loaded, and the content enumeration is informative rather than filler. The single run-on sentence with an eight-item list and unexplained jargon like 'the fence' and 'binding-strength wording' costs it a point on readability.

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, documentation-fetch tool with no output schema and no annotations, the description supplies what the agent needs: what is returned at a high level, that it is free, and by which HTTP route. The only real omission is the concrete response 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 and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals a parameterless fetch rather than implying any query or filter options.

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?

The description names a specific resource — the published criteria document for the Probe Grade service (memory-probe-grade/v1) — and enumerates its contents (input contract, five probes, expectation tables, fence, corpus identity), which clearly separates it from the action tool probe_grade_grade. It does not name the sibling tools probe_grade_grade or probe_grade_precheck outright, so sibling differentiation is implied rather than stated.

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' gives a concrete precondition that positions this tool ahead of the paid grade call, and 'every report is reproducible from them' explains the payoff. There are no explicit exclusions or named alternatives, and no guidance on whether the precheck tool is a substitute or a complement.

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