sac_export_download

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

With no annotations, the description carries full burden. It discloses return format (base64-encoded bytes, size, content type) and package type (TGZ archive), but does not mention side effects, permissions, or safety profile (e.g., whether it is read-only or idempotent).

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 sentences that are succinct and informative. First sentence states action and return value; second sentence adds relevant detail about the package format. No unnecessary words.

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 and no annotations, the description covers the essential aspects: purpose, return format, and precondition (completed job). However, it lacks information about error conditions (e.g., what if job not completed) or whether the download is synchronous.

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. The description adds no additional meaning beyond what the schema already provides for the two parameters.

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?

Clearly states it downloads the result package of a completed Content Network export job. Distinguishes from sibling tools like sac_export_start (initiation) and sac_export_status (status check) by specifying it is for downloading after completion.

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 clearly indicates it is for use after a job has completed, but does not explicitly exclude alternatives or state when not to use it. The parameter downloadUrl is described in schema as coming from sac_export_status upon completion, providing implicit guidance.

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