iiif-image-fetch

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

No annotations are provided, so the description must carry the full burden. It only hints at 'automatic size constraints' but does not explain what happens when constraints are exceeded (e.g., resizing, error), nor does it mention authentication needs, rate limits, or side effects. The schema already describes maxDimension and maxPixels, so the description adds minimal behavioral context.

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 single 9-word sentence, concise and front-loaded. However, it could be more informative while remaining concise (e.g., mentioning the return type). No waste but slight under-specification.

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?

Given the complexity (8 parameters, no output schema), the description is incomplete. It does not explain what the tool returns (binary image data? file format? response structure) or how to handle the output. The tool is a fetch operation, but no mention of whether it downloads or returns a URL.

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% (all 8 parameters are described in the schema), so baseline is 3. The description adds the phrase 'with automatic size constraints', which loosely connects to maxDimension and maxPixels but does not provide new meaning beyond the schema. No additional parameter semantics are given.

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 uses a specific verb ('Fetch') and resource ('IIIF image data') with a differentiator ('automatic size constraints'). It clearly distinguishes from sibling tools like iiif-image (which likely deals with image metadata or info) and other IIIF tools.

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?

No guidance on when to use this tool vs alternatives like iiif-image or iiif-manifest-canvases. The description does not mention when not to use it or provide any contextual usage hints.

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