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

Annotations already establish readOnlyHint and openWorldHint, and the description adds valuable behavioral context: the exact id forms accepted, the instruction not to prepend the loc.gov URL, the detailed set of returned fields, and the conditional presence of digital-resource links. It stops short of describing not-found or error behavior, but that is a minor gap for a read-only retrieval tool.

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 front-loaded with the core purpose and then gives structured usage details. The enumerated return fields add length but provide useful expectations about what the full metadata record contains. It is somewhat dense, but every part earns its place with no 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?

For a single-parameter retrieval tool with a rich output schema and annotations covering read-only behavior, the description is complete: it states when to call it, what input to pass, what the output includes, and which results are out of scope. Nothing critical is missing for an agent to invoke it correctly.

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%: the input schema already explains the id sources, simple-ID versus newspaper-path forms, verbatim passing, and the no-URL-prefix rule. The description reinforces the same guidance but adds no new parameter meaning beyond the schema, 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 opens with a specific verb and resource: 'Retrieve the full metadata record for a specific LOC digital item.' It distinguishes itself from search by requiring a prior libofcongress_search result and from newspaper-page retrieval by explicitly stating that non-item results such as newspaper pages have no item record and cannot be retrieved here.

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?

It gives an explicit workflow: 'Use after libofcongress_search on a result whose is_item is true.' It also gives a clear when-not condition, enumerating collections, exhibits, guides, and newspaper pages as invalid. The alternative for newspaper pages is inferable from the sibling list, and the exclusion is stated directly.

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