Download scrape as CSV/XLSX

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

Annotations already indicate non-read-only and non-idempotent, but the description adds crucial details: it downloads the file (authenticated), never overwrites (appends -1, -2 suffix), and returns the path. This goes beyond annotations to describe side effects and file handling.

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?

Three sentences, front-loaded with the core purpose, and each sentence adds value: main action, download behavior, precondition, and file naming. No fluff or redundancy.

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 tool with 3 parameters and no output schema, the description covers the key aspects: what it does, when it works, how files are named, and the return value (path). It omits error cases but states the precondition clearly. With siblings present, it is sufficiently distinct and 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?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds little about parameters beyond mentioning the full column layout (which is output-related). Baseline 3 is appropriate since the schema already handles semantics.

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 ('Save a finished scrape as a spreadsheet file on this computer and return its path') with a clear resource and output. It distinguishes itself from siblings like get_results by explaining it downloads the file rather than returning a link.

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?

It provides a clear precondition ('Only works once the scrape status is done') and explains the download behavior. However, it does not explicitly mention alternatives or when not to use it, but the context implies it is for file retrieval versus data access.

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