describe_manifest

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

No annotations are supplied, so the description carries the full behavioral burden. It mentions pagination, but the limit/offset parameters already imply that; it says nothing about fetching a remote URL (network access, latency, possible SSRF concerns), what happens with an invalid or unsupported IIIF manifest, or whether access is authenticated.

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?

A single front-loaded sentence with zero filler: verb, resource, returned fields, and pagination in one clause. Nothing could be removed without losing information.

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?

The output schema covers return values, but with 0% parameter coverage and no annotations, the description should explain the required manifest_url semantics and pagination contract. For a remote-fetch tool with an unconstrained string parameter, this is too thin.

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 0% across three parameters, so nothing documents manifest_url, limit, or offset. The description's only hint is the word 'paginated', which does not explain the required manifest URL format (IIIF v2 vs v3), default/max limit values, or offset semantics.

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?

Specific verb plus resource plus scope: 'List the canvases of a IIIF manifest', with the returned fields (id, label, size) named. An agent can tell this apart from view_region and annotate_transcription, though the description never explicitly contrasts them.

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 statement of when to use this versus the siblings, no prerequisite about needing a valid IIIF manifest URL, and no guidance on paging through results. 'Paginated' hints at iteration but gives no instruction on how to proceed.

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