kasko_download_archive

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

Annotations already indicate a write operation (readOnlyHint: false) with no destructiveness (destructiveHint: false). The description adds that it saves a spreadsheet to disk, which is consistent and provides useful context about output format. It does not go into details like file naming or overwrite behavior, but given the annotations, the transparency is strong.

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?

Two sentences, no fluff, front-loaded with the action. Every word serves a purpose. Perfectly concise for the tool's simplicity.

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?

Given the low complexity (3 parameters, simple semantics), perfect schema coverage, existing output schema, and clear annotations, the description covers all necessary aspects. It includes usage guidelines and sibling differentiation, making it fully self-contained for an AI agent.

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 baseline is 3. The description does not add extra meaning to parameters beyond what the schema provides (year, month, destination). It correctly implies monthly granularity, but this is already clear from the parameter names and tool title.

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 'Download a monthly kasko list spreadsheet to disk,' providing a clear verb and resource. It distinguishes itself from sibling kasko_search_archive by noting when to use each, making the purpose unambiguous.

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 explicit when-to-use guidance ('when the user wants the whole list as a file rather than a few rows') and explicitly names an alternative tool for a different case ('Prefer kasko_search_archive when they only need specific vehicles'). This fully satisfies the criteria.

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