HathiTrust Full Catalog Record

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful operational context ('Data: HathiTrust Bibliographic API, no auth required'), which goes beyond the schema, but does not disclose other behavioral aspects like rate limits or response structure, which are partially covered by the output schema. This matches the mid-level baseline.

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 compact, with the core purpose front-loaded in the first sentence, followed by usage guidance and data source. Every sentence adds value, there is no filler, and the structure is logical.

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 description covers what the tool does, when to use it, data source, and authentication requirement. With an output schema present and annotations covering safety, no critical information is missing for an agent to invoke the tool correctly. It also distinguishes from siblings effectively.

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 coverage is 100% with detailed descriptions and examples for both id_type and id_value. The description reiterates the identifier types but does not add any new parameter semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Get') and resource ('full HathiTrust catalog record'), enumerates the supported identifier types, and lists the additional MARC-derived fields. It explicitly differentiates from lookup_by_id by noting it includes everything that function returns plus more, making the tool's scope unmistakable.

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?

Provides clear guidance on when to use this tool ('Use this when you need bibliographic detail beyond title/ISBN, not just item availability'), implying when not to use it. It references lookup_by_id as a point of comparison, but does not explicitly name an alternative tool or say 'use X instead', so it falls short of a 5.

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