Download CASDA product

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

The description goes well beyond annotations by detailing behaviors: never overwrites by default, enforces byte limit, verifies Content-Length, resumes on Range support, removes incomplete files after failure. This provides essential safety context for a file download operation.

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 short, front-loaded sentences covering purpose and key behaviors. Every sentence adds information; no fluff. Highly efficient.

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 tool's moderate complexity (download with options) and the presence of an output schema, the description covers prerequisites, safety, and behavioral quirks comprehensively. It is sufficient for an agent to use correctly.

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 covers 100% of parameters with good descriptions. The description adds clarity on constraints (destination constrained to CASDA_DOWNLOAD_DIR) and default behavior (verify_checksum default true). This adds value beyond the schema.

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 clearly states the action: 'Download one confirmed-ready product using guarded, streamed local filesystem writes.' It uses specific verb+resource and distinguishes from sibling tools like casda_get_product (which likely returns metadata) and staging 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?

The description mentions prerequisites ('requires CASDA_ENABLE_DOWNLOADS and a restricted CASDA_DOWNLOAD_DIR') and implies the product must be confirmed-ready (via staging). It does not explicitly list alternatives or when-not-to-use, but the context of sibling tools provides differentiation.

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