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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the batch behavior and that it returns the same per-identifier data as lookup_by_id, plus the 1-10 limit. It doesn't mention potential partial failures or edge cases, but given the strong annotation coverage, this is sufficient. No contradiction with annotations.

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 two sentences, front-loaded with the core purpose and scope, then immediately provides usage guidance and data source. Every sentence earns its place; no redundancy or filler.

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 output schema exists and annotations cover safety and idempotency, the description is complete. It covers the batching capability, return structure (same as lookup_by_id), data source, auth requirements, and when to use it. Nothing an agent needs to correctly invoke this tool 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?

The input schema provides full descriptions for each parameter (id_type and id_value) and enumerates allowed types. The description adds the 'any mix' clarification and the 1-10 limit, but those are already reflected in the schema's minItems/maxItems. Since schema coverage is 100%, the description adds marginal value beyond what the schema already documents.

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 clearly states the verb (look up), resource (HathiTrust catalog), and scope (1-10 identifiers in a single call). It explicitly differentiates from lookup_by_id by batching multiple identifiers, making the tool's distinct role unambiguous.

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?

The description provides explicit usage guidance: 'use this instead of repeated lookup_by_id calls when checking availability for a reading list or citation set.' It also notes 'no auth required,' which sets expectations for access. This tells the agent exactly when to choose this tool over the sibling.

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