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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only labels the output as metadata; it does not explain whether this is a read-only lookup, how the input affects the result, what happens when no item is found, or any other behavioral expectations.

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 short, but it is under-specified rather than efficiently complete. It reads as a label or category title, not as a usable tool description.

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 tool is simple, but the missing parameter semantics and absent usage context make it insufficient for reliable invocation. Even with an output schema, the agent still cannot determine what value to supply for q.

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 schema defines one parameter, q, with 0% documented coverage, and the description does not explain q at all. An agent cannot tell whether q is an item identifier, a search query, a URL, or something else.

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 identifies the resource ('Internet Archive item') and the kind of data ('metadata'), but it lacks a verb or explicit operation such as 'retrieve' or 'search'. It is less vague than a tautology, but it does not clearly state what the tool does with the input.

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?

There is no guidance about when to use this tool or why it should be chosen over related siblings like wayback, cdxwayback, or commoncrawl. The intended use is only implied by the phrase 'item metadata'.

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