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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the auth model (free account required, anonymous and API-key-only calls refused) and the shape of the answer (existence flag, readable copy count, reading URLs). Return format is disclosed despite there being no output schema.

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 dense sentences, front-loaded with the core purpose, then the outputs, then the access constraint. Every clause carries information; the only weak spot is the terse "Keyless." fragment, which sits awkwardly next to the account requirement.

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 compensates by enumerating the return values (existence, readable copy count, direct URLs), and it covers the access prerequisite that would otherwise cause a failed call. Nothing essential for correct invocation is missing.

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% and the enum for id_type is fully documented in the schema, so the schema does the heavy lifting. The description only says "given an identifier" and adds no syntax, format, or fallback guidance beyond the structured fields. Baseline 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?

States a specific verb and resource: given an identifier, report whether a readable full-view copy exists on HathiTrust, how many copies are readable, and direct reading URLs. That output signature is distinctive enough to separate it from generic identifier tools like lookup_by_identifier, though no sibling is named 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?

"Convenience check" implies a lightweight, targeted use case, and the description states the access precondition (free Pipeworx account; anonymous and X-API-Key-only calls refused). It never says when to prefer this over lookup_by_identifier or archive_evidence, so routing is left to inference.

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