dpla_get_item

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

With no annotations, the description carries the full behavioral burden, and it does disclose the auth requirement (API key), which is genuinely useful and not present in structured fields. It says nothing about error behavior, rate limits, or what happens with an invalid/missing id, so it is only partially transparent.

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 short, front-loaded sentences with zero filler. The core action comes first and the prerequisite second.

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 single-parameter retrieval tool with an output schema present, the description covers the essential action and the auth prerequisite. The return shape is handled by the output schema, so the only real gap is the lack of id-format detail and sibling routing.

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% and the single parameter item_id has no schema-level documentation. The phrase 'by its id' hints that item_id is an identifier, but nothing about format, source, or example is added, so the description does little to compensate for the coverage gap.

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?

States a specific verb and resource ('Get one DPLA item by its id'), which is enough for an agent to know it retrieves a single item rather than listing or searching. It does not explicitly distinguish itself from the sibling dpla_search, but the singular 'one item by its id' does imply the difference.

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 gives a prerequisite ('Needs DPLA_API_KEY') but no guidance on when to use this versus dpla_search, or when an item id is the right input. No alternatives or exclusions are named, so the agent must infer usage from the tool name alone.

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