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

With no annotations, the description carries the full burden and is unusually transparent: it discloses the USDC payment requirement and address, the X-PAYMENT header requirement, HTTP 402 for unpaid requests, and that a valid payment causes the same URL to return JSON. It does not describe rate limits or exact JSON fields, but the main behavioral quirks are covered.

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 text is short and front-loaded with the URL and payment requirement before explaining modes. Almost every clause adds a distinct fact (price, purpose, chunk selection, error, output); only the 'Not a new SKU' line is marginal.

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 paid endpoint with no output schema, it covers all four parameters' effects, costs, the payment mechanism, and the 402/JSON behavior, which is enough for an agent to invoke it. It stops short of spelling out the JSON response structure or how to discover catalog ids, but these are secondary.

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 input schema has 100% parameter description coverage and already repeats the pricing/mode semantics for id, page, before, and x_payment. The tool description reinforces rather than adds meaning beyond those schema descriptions, so the baseline 3 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?

The description names a specific resource ('Ofsted school / provider inspection report text') and the exact GET URL, and it enumerates the main access modes (plain GET, ?id, ?before). It does not explicitly contrast the tool with sibling helpers such as get-one or get-page, so it falls just short of full differentiation.

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?

It gives concrete invocation guidance: a plain GET yields the newest chunk, ?before fetches an older chunk, and ?id returns one official text, with costs attached. It also states the 402 failure mode when unpaid. No alternatives outside this endpoint are mentioned, so it lacks explicit when-not-to-use guidance.

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