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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real value by disclosing the shape of the response — a bounded 'sample' of published items with canonical URLs — which tells the agent results are partial, not exhaustive. It does not mention pagination, truncation behavior beyond the sample, or auth requirements.

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?

One sentence for what the tool returns, one for when to use it. Front-loaded with the verb and resource, no filler, nothing redundant.

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 carries the burden of describing returns, and it does so adequately: entity fields plus a bounded sample of archive items with canonical URLs. Minor gap: it doesn't say whether the sample is paginated or how the item limit interacts with the broader collection.

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%, so both parameters are already documented (including the default of 20 and max of 50 for itemLimit). The description's phrase 'a sample of its published archive items' conveys the purpose of itemLimit but adds no syntax or constraint detail beyond the schema, 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 gives a specific verb (fetch), resource (a single institution by slug), and enumerates what comes back (description, history, contact details, sample archive items with canonical URLs). 'Single institution by slug' implicitly contrasts with the list_institutions sibling, but it never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Two concrete use cases are given: answering questions about a specific institution's holdings and finding items available for licensing. This is clear positive guidance, but there are no exclusions or named alternatives (e.g. when to prefer search_archive or list_institutions instead).

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