DPLA — Fetch Item by ID

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the result is a 'full metadata record' and lists returned fields, but with an output schema present this is largely redundant. No behavioral trait beyond the annotations and schema is meaningfully disclosed.

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?

Three sentences, front-loaded with the core action and identifier format, followed by return fields and usage context. The field list is somewhat redundant with the output schema, but the description remains compact and every sentence earns its place.

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?

Given a single required parameter, a fully described schema, rich read-only/idempotent annotations, and an output schema, the description covers the essential workflow: fetch one item by ID after searching. It could be slightly more explicit about sibling tool differentiation, but nothing critical an agent needs to call it correctly is missing.

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%, and the item_id parameter already includes the 32-character hex format, an example, and instruction to obtain it from search results. The description repeats the format but does not add significant new meaning beyond what the input schema already provides, so the baseline score of 3 is appropriate.

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 and resource: 'Fetch the full metadata record for a specific DPLA item by its 32-character hex identifier.' This clearly distinguishes the tool from siblings like dpla.archives.search, dpla.archives.facets, and dpla.archives.by_subject because it targets a single item by ID rather than a query or facet operation.

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 provides clear when-to-use context: 'Use after a search call to retrieve complete details for a specific digitized object.' This tells the agent the intended workflow, though it does not explicitly name alternatives or state when not to use the tool, so it falls just 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.