volume_pages

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

No annotations exist, so the description carries the full burden. 'Show' implies a read-only lookup, and it enumerates the returned fields, but it says nothing about behavior for an unknown id, whether the mapping can be very large, or whether a manifest URL triggers a network fetch. With an output schema present, the return-value gap is partly covered.

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 compact sentence that front-loads the returned content, followed by a short parameter hint. The '(Bild:Sida)' gloss and stray line break are minor noise but nothing is 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?

For a one-parameter read tool with an output schema, the description covers purpose, output content, and accepted input forms. Missing only edge-case behavior (invalid id, large volumes) and sibling routing, which keeps it below a 5.

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?

The single parameter has 0% schema description coverage, so the description must compensate — and it does, giving a concrete example id format ('A0006950') and an alternative input form (manifest URL) that the bare string schema does not convey.

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 ('Show') and a concrete payload: a volume's title, date range, remarks, and image-number-to-printed-page mapping. That is clearly distinct from siblings like get_page (single page) and search_records, though the description never names those siblings explicitly.

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 only implied: it tells you to supply a volume id or manifest URL, which suggests 'call this to resolve a volume before fetching pages'. There is no explicit when-to-use versus get_page or browse, and no stated prerequisites or failure conditions.

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