Download Stem Outputs

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

No annotations provided; description adds that presigned URLs are re-fetched to avoid expiry, which is helpful. However, it doesn't disclose what happens if the job isn't complete or if there are permission requirements.

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: first states purpose, second adds behavioral detail. No unnecessary words 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?

Given no output schema, description doesn't explain return value (presumably success/confirmation). But for a download tool, that's acceptable. Covers job completion constraint and presigned URL behavior.

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 baseline is 3. Description doesn't add extra meaning beyond schema; the three parameters are sufficiently documented in 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?

Clear verb+resource: 'Download the output stems' with context that job must be COMPLETED. Distinct from sibling tools like separate_stems (creation) and get_job (metadata).

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?

Implicitly states when to use: for completed jobs. Lacks explicit exclusions (e.g., 'do not use for incomplete jobs') and doesn't name alternatives, but the context is clear.

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