Get LOC Item Detail

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool returns metadata and asset URLs, and notes 'LOC public domain' regarding data rights. It does not contradict annotations, but it does not significantly expand on behavioral traits beyond what annotations provide.

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 a single sentence that conveys all essential information. It is concise, front-loaded with the main action, and every word adds value.

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 the tool's purpose, input parameter, and output contents. An output schema exists (not shown but present), so return values are documented. There are no missing elements considering the tool's simplicity and the richness of annotations.

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 is fully covered (100% description coverage) with a clear explanation of the item_id parameter. The tool description does not add new information beyond the schema, so it meets the baseline expectation.

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 explicitly states the verb 'Get', the resource 'Library of Congress item', and the outputs: 'full metadata + asset URLs (image, audio, PDF)'. It also specifies the input format (ID or URL). This clearly distinguishes it from sibling tools like media.loc.search (search) and media.loc.collections (collections).

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?

Usage is implied by the tool's purpose: use when you have a specific item ID or URL. However, there is no explicit guidance on when not to use this tool versus alternatives (e.g., media.loc.search for discovery). The description does not provide exclusions or context for choosing this over siblings.

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