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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds behavioral context beyond annotations: it specifies the source API (Internet Archive metadata API) and enumerates the exact fields returned, including the list of downloadable files with format and size. This gives the agent a concrete expectation of the response shape. It doesn't mention rate limits or error behavior, but for a read-only metadata lookup with an output schema present, this is adequate.

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, information-dense sentence that front-loads the core action ('Get full metadata for an Internet Archive item by identifier') and then lists the returned fields. Every clause earns its place; there is no filler or repetition of the tool name.

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, read-only, idempotent lookup tool with a rich output schema, the description is complete. It tells the agent what the tool does, what fields to expect, and how to obtain the identifier. The annotations cover safety, and the output schema covers return structure. Nothing essential 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%, so the schema already documents the single parameter well. The description adds value by clarifying that the identifier is an 'archive.org item identifier' and the parameter description in the schema gives concrete examples and tells the agent how to obtain it from search results or a details URL. The description itself doesn't repeat parameter details, but the schema carries the load; the combination is strong.

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 ('Get'), a specific resource ('full metadata for an Internet Archive item by identifier'), and enumerates the content fields (title, creator, description, date, mediatype, subjects, license, collection, downloadable files with format and size). It also names the underlying API (Internet Archive metadata API). This clearly distinguishes it from sibling tools like archiveorg.archive.search and archiveorg.wayback.check_availability.

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 context: it is the tool to call when you have an item identifier and need its full metadata. The parameter description explicitly tells the agent where to get the identifier (from archiveorg.search results' identifier field, or the tail of an archive.org/details/{identifier} URL), which is strong usage guidance. However, it does not explicitly state when NOT to use it or name alternatives (e.g., use archiveorg.archive.search to find items).

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