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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add scope — and it does, by enumerating exactly what the response contains, including derived data like how each text layer was made and the IIIF manifest. It stops short of stating error behavior for a bad id or whether any fields can be absent.

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 dense sentence with the resource stated first and the payload list following; nothing is padded or repeated. It is a sentence fragment without a verb, which is efficient but slightly telegraphic.

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 must convey return content, and it does so thoroughly for a read-only single-record fetch. What remains missing — id validation, missing-record behavior, and any explicit pointer to search_manuscripts as the id source — is minor for a simple one-parameter getter.

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?

There is a single required parameter at 100% schema coverage, and the schema already explains that the id comes from search_manuscripts or a page URL. The description adds no format details, accepted id shapes, or failure modes beyond that, 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 names a specific resource — one manuscript — and enumerates the content it carries (facts, text layers, URLs, IIIF manifest, licence, citation), so an agent can tell it is a single-record detail fetch rather than a search. It never uses a verb and never explicitly contrasts with search_manuscripts, which keeps it short of a 5.

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?

"One manuscript" implies a singular lookup and the listed payload implies a detail-view use case, but there is no explicit when-to-use or when-not guidance and no named alternative. The routing hint ("An id from search_manuscripts or a page URL") lives only in the schema, not the description, so the agent must infer that search_manuscripts is the way to obtain an id.

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