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

No annotations are provided, so the description bears the full burden. It clearly communicates the operation is a safe-looking download, but does not disclose details like required job completion state, file encoding or naming, or what happens if the job has no results. The core behavior is clear enough for a simple read-style tool.

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 compact and well-structured: one clear opening sentence followed by two focused bullets. Every sentence contributes functional guidance, and the key usage criteria are 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?

With an output schema present, full schema coverage, and a simple two-parameter interface, this description covers the essential usage context. It misses a small amount of operational nuance, such as whether the job must be completed or whether the CSV includes headers, but nothing critical blocks correct invocation.

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%, with both `job_id` and `api_key` documented. The description adds no extra parameter-level detail, but the schema already fully explains the parameters, so the baseline score of 3 is appropriate.

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?

States a specific verb ('Download'), a resource ('a job's results'), and an output format ('CSV'). The phrase 'full job output' makes the scope clear unless the agent needs a different format. It effectively distinguishes itself from sibling pull tools.

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?

Explicitly provides 'Use when' conditions and names the alternative `pull_results`, including the exact condition for preferring this tool (spreadsheet/CSV format). This gives concrete routing guidance with minimal ambiguity.

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