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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, covering the full safety profile. The description adds essentially nothing behavioral on top of that: no pagination, no return shape, no indication of how the 'query' object is interpreted. It is consistent with the annotations but adds no new context.

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?

A single front-loaded fragment with zero filler. It is efficient, though the terseness borders on under-specification rather than pure conciseness.

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 catalogue tool with no output schema, the description should at least convey what the listing contains and how the query object filters it. Neither is present, and with 0 required params the description is the only place an agent could learn what query keys are accepted. The gap is meaningful even for a low-complexity read tool.

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 per the baseline the schema is presumed to carry parameter meaning, giving a floor of 3. In practice the single 'query' parameter is a free-form object with no defined properties, and the description offers no hints about supported keys, so the description does not compensate for the schema's permissiveness.

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 verb 'List' and the resource 'A-Level checks, tariff data' are identifiable, so an agent can tell this is a read/list surface. However, 'education proof surfaces' is opaque jargon and the description never distinguishes this catalogue from the sibling alevel_check_offer (the check action) or the many other *_catalogue tools. The purpose is only partially clear.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives such as alevel_check_offer. The agent must infer from the name alone that this is a discovery/list tool rather than an evaluation tool.

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