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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses that descriptions can be truncated and must be paged (a real behavioral trait beyond annotations), but says nothing about not-found behavior, name-vs-slug precedence, or locale effects on the returned content.

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?

Two short sentences; the core retrieval purpose and returned fields come first, with the paging instruction second. Nothing is redundant or padded.

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?

It compensates well for the absence of an output schema by listing the fields returned, and it warns about truncation. The remaining gap is that zero parameters are marked required, yet the description never states that at least one of name or slug must be supplied.

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 all five parameters are already documented, including the nextOffset continuation hint. The description only restates the paging role of offset/maxChars and adds no meaning about precedence between name and slug or about how locale changes results.

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?

Names a specific verb and resource ("Get full details for one digital archive item"), states the two lookup keys (slug or name), and enumerates the returned fields. The singular "one ... item" implicitly separates it from search-archives, but no sibling is named, so differentiation is left 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?

Provides concrete usage for the pagination parameters ("Use offset and maxChars to page through long descriptions"), which is real when-to-use guidance. It gives no guidance on when to prefer search-archives over this tool, nor on what to do when a lookup fails or when both name and slug are supplied.

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