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

Annotations only supply readOnlyHint=true, leaving the description to carry the behavioral burden, and it does disclose real detail: which fields belong to the current form's source, that version_count/source_count/first_edition_seen/last_edition_seen appear only for records with multiple forms or sources, and that the Union retains records absent from any current catalog. This is substantive context beyond what the annotation provides, though it is expressed obliquely.

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 description is a dense, meandering block of very long sentences with no clear front-loaded summary of what the tool does. Field-level conditional behavior is packed into prose that an agent must parse carefully, and key information (the actual purpose) is buried behind return-value detail.

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 must describe the return value, and it does cover the row's shape, the conditional multi-form/multi-source fields, and the stale-edition note. However, the coverage is cryptic and omits basics such as the response wrapper or how the institution-sharing data is structured, leaving meaningful gaps for a 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% with a single documented parameter ('A catalog id from find_catalogs'), so the schema already does the heavy lifting. The description adds no syntax, format, or sourcing detail beyond what the schema supplies, so the baseline of 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 opens with 'One catalog edition' and enumerates what the returned row contains, so the resource is identifiable, but it never states a clean verb like 'retrieve a single catalog by id' and never explicitly distinguishes itself from the sibling find_catalogs. An agent can infer it is the single-record getter, but mostly from the sibling name rather than the description.

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 indication of when to use this tool versus find_catalogs, nor any prerequisite beyond the schema's 'catalog id from find_catalogs'. The line 'the forms themselves ... come from the one-record get' gestures at another tool but is cryptic and doesn't establish a selection rule.

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