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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about side effects, rate limits, input requirements, or returned behavior beyond the noun phrase 'snapshot history.' For a tool with no annotations, this is a significant transparency gap.

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, which is good, but brevity crosses into under-specification. It is a fragment rather than a clear sentence, and the few words provided do not carry enough semantic weight to justify the absence of a full explanation.

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?

Although an output schema exists, which reduces the need to document return values, the input semantics remain unexplained. The single parameter q is ambiguous, and the description lacks enough context for an agent to confidently select and call this tool rather than a sibling like cdxwayback.

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?

There is one parameter, q, and the schema provides no description, with 0% schema description coverage. The description never mentions q, what values it accepts, whether it expects a URL, domain, or search term, or how it affects the request. The agent has no guidance for invoking the tool correctly.

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 as 'Archive.org snapshot history' and links it to the Wayback Machine, so the general domain is clear. However, it is a noun phrase with no verb, so an agent cannot tell exactly what operation is performed (retrieving snapshots, listing history, querying availability, etc.). It also does not differentiate this tool from closely related siblings like cdxwayback or wayback_leaks.

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 phrase 'snapshot history' implies the tool is used for browsing or retrieving archived snapshots from Archive.org. There is no explicit statement of when to choose this tool over alternatives, no exclusions, and no mention of prerequisites or intended query type.

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