Download CASDA job results

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

Annotations provide idempotentHint=true and destructiveHint=false; description adds sequential download, stop-on-failure, and partial success reporting. This adds some behavioral context but does not cover authentication, side effects on local storage, or concurrency limitations.

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 concise sentences, front-loaded with the core purpose. Every word adds value; no redundant or verbose content.

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 download tool with an output schema, the description covers key behaviors (sequential, stop on failure, partial results). It lacks detail on error handling, default directory location, or post-download file management, but is sufficient for basic use.

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 coverage is 100% with parameter descriptions. Description does not add any additional semantic details beyond the schema, such as format constraints for request_id or the effect of verify_checksum.

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?

Description clearly states the tool downloads all ready results for a single job, with specific details like sequential download and target directory. It distinguishes from sibling tools like casda_get_data_job_results (which likely only retrieves results metadata) and casda_download_product (single product download).

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?

No explicit guidance on when to use this tool versus alternatives like casda_get_data_job_results or casda_download_product. The description assumes the user already knows to use this for downloading completed job results.

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