file_download

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

The description adds real behavior beyond the annotations: full byte verification and an atomic, no-overwrite commit, which tells the agent existing files will not be clobbered and partial writes won't be left behind. It does not disclose failure modes (what happens on verification failure or partial transfer), whether the transfer is resumable, or how the download interacts with the sibling pause/resume/cancel tools, all of which matter for a non-idempotent, open-world write.

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?

One dense sentence, front-loaded with the action and destination, with the integrity/atomicity guarantees trailing as qualifiers. Nothing is padded, though the compression contributes to the jargon problem.

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 five-parameter, non-idempotent, open-world file-writing tool with no output schema and no documented return values, the definition covers the core guarantee but omits how to obtain a 'reference', what operationId is for, and how progress/failure is surfaced. An agent could invoke it, but not confidently handle limits or recovery.

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 0% across 5 parameters, so the description bears the burden. It partially covers 'path' ('a new local path') and 'reference' (the App package reference to download), but says nothing about 'purpose' (app-package vs app-workspace), 'maxBytes' (capped at 128 MiB), or 'operationId', leaving three parameters with no semantics anywhere.

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 names a concrete verb (Download), a resource (an authorized App package reference), and a destination (a new local path), so an agent can tell it moves data onto the local filesystem. The phrasing 'authorized fixed App package reference' is jargon that is never defined, and no sibling (file_upload, apps_file_export, apps_file_commit) is mentioned for contrast.

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?

There is no statement of when to use this rather than file_upload, apps_file_export, or apps_file_commit, and no mention of the file_pause/file_resume/file_cancel companions that clearly relate to long transfers. The only usage signal is indirect, via the word 'authorized', which hints that callers are pre-approved but never says how.

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