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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the provenance requirement for the id and that the record returned is 'full' rather than a summary, but says nothing about error behavior for missing ids or how the returned record is scoped.

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 sentence with zero filler that front-loads the verb, the resource, and the input constraint. Nothing could be removed without losing information.

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?

The tool is simple and annotations cover safety, but with no output schema the phrase 'full catalogue record' is the only indication of return content and remains undefined in shape or size. An agent knows how to call it but not precisely what it gets back.

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 coverage is 100% and the single parameter already documents itself as 'Record id from search.', so the baseline is 3. The description reinforces the provenance of the id but adds no syntax, format, or lookup semantics beyond what the schema states.

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 ('Fetch') and resource ('the full catalogue record') with the key input qualifier ('for an id returned by search'). An agent can distinguish it from 'search' since it retrieves one record rather than listing, though it doesn't differentiate itself from siblings like 'get_dataset'.

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?

Usage is implied through the chaining constraint that the id comes from a prior 'search' call, which is a real workflow hint. However, there is no explicit when-to-use vs when-not guidance, no mention of what happens with an invalid or non-search-derived id, and no mention of alternatives.

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