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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's added value is disclosing the shape of the returned data (paper counts, durations, marks, calculator rules, tiers) in the absence of an output schema, but it says nothing about behavior such as coverage of exam boards, fallback when a board/level/subject combination is unknown, or result size.

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 dense sentence with no filler, front-loaded with the resource and followed by the payload breakdown. It is efficient, though the fragment style omits any action verb.

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?

With no output schema, the description usefully enumerates the returned metadata fields, which is the strongest part of the definition. It is nonetheless incomplete for a zero-required-parameter lookup: no accepted parameter values and no guidance distinguishing it from its two siblings.

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 0% for all three parameters (board, level, subject), so the description carries the full burden and does not compensate at all. It never mentions the parameters, accepted values (e.g., 'AQA', 'GCSE', 'Higher'), casing, or what happens if one is omitted when zero parameters are required.

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 identifies the resource clearly ('UK exam specification metadata') and enumerates the payload (spec codes, paper structure, topic lists, links), so an agent knows what data it retrieves. However, there is no explicit verb and no differentiation from the sibling tools exam_paper_index and exam_topic_paper, leaving the boundary between them 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?

There is no guidance on when to use this tool versus exam_paper_index or exam_topic_paper, and no prerequisites or conditions are stated. The only implied usage comes from the word 'specification' in the content list.

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