loc_get_item

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

No annotations are provided, so the description carries the full burden. It states what the tool returns ('metadata and all image file URLs') and gives an example URL format, but does not disclose potential error behaviors, URL validity requirements, or any side effects. This is adequate but not rich.

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 concise, front-loaded sentences. The verb 'Fetch' starts the description, and the example URL provides concrete guidance without unnecessary verbosity.

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 simple one-parameter tool, the description is largely complete: it states the purpose, input format, and return payload. However, it would be stronger if it noted behavior for invalid URLs or explicitly linked to the download_image sibling for handling returned image URLs.

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 0%, but the description effectively documents the single parameter by defining it as a 'full URL' and providing an explicit example. This gives the agent enough semantic understanding to construct a valid itemUrl value.

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 a specific action ('Fetch') and resource ('a Library of Congress item'), and specifies the key input method (by full URL). The example URL further disambiguates the tool, distinguishing it from sibling search tools like loc_search.

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 implies usage when the agent has a full item URL, which provides clear context. However, it does not explicitly mention alternatives or exclusions, such as 'use loc_search when you only have a query'.

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