search_archives

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

With no annotations, the description carries the full behavioral burden and does usefully disclose two traits: results are deduplicated by digest and the total is capped at 100 captures. However, it does not describe the return format, what fields a capture includes, or any error behavior, leaving notable gaps.

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 two short sentences with no filler. Every element ('exact URL', 'deduplicated by digest', 'at most 100 captures') conveys necessary information in minimal space, and the key action is front-loaded.

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 read-only search tool, the description covers the core function, a key behavioral trait (dedup), and a numeric cap. It lacks an output schema and does not spell out return fields, and the limit parameter semantics are not fully explicit, but the overall complexity is low enough that the tool can be invoked correctly with the information provided.

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 has zero descriptions for either parameter, so the description must compensate. It clarifies that url must be an exact URL and implies an upper bound on results, but it never explicitly defines the limit parameter's meaning or its relationship to the default of 20, leaving partial ambiguity.

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 action ('Find') on a specific resource ('Wayback captures') with a clear constraint ('exact URL') and an explicit deduplication behavior. This clearly differentiates the tool from siblings like search_web, inspect_page, and lookup_domain, which target other resources.

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 clear context that the tool is for archived captures of a specific URL, implying use when historical snapshots are needed rather than live web results. It does not explicitly name alternatives or exclusions, but the 'exact URL' qualifier and Wayback focus make the selection context clear.

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