archive_list

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

With no annotations, the description must carry the behavioral disclosure burden. It states 'List' which implies read-only, and it documents date range filtering, but it does not explicitly state side effects, sort order, or behavior with no matching entries. The output schema covers return structure, but not behavioral traits.

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 extremely compact and well-structured: one sentence states the purpose, followed by a short Args list. Every sentence is necessary, and the key information 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?

This is a simple list tool with three optional parameters and an output schema. The description covers purpose and all parameters adequately. The only gap is the lack of usage guidance or explicit differentiation from sibling tools, but given the low complexity, the description is nearly complete.

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 input schema has no per-property descriptions (0% coverage), so the description's Args section adds meaningful semantic value: it specifies date format (YYYY-MM-DD), inclusivity for date_to, and the default for max_results. All three parameters are explained, exceeding the schema's bare types and defaults.

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 explicitly states 'List archived web fetch/search entries with metadata,' naming both the verb ('List') and the resource ('archived web fetch/search entries'). This clearly distinguishes the tool from sibling 'archive_read', which presumably reads a single entry.

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 no guidance on when to use this tool versus alternatives like 'archive_read' or the web_fetch/web_search tools. It simply lists parameters without addressing use cases, exclusions, or preferred contexts.

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