acc_download_file

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

Annotations already declare readOnlyHint=true. The description adds meaningful context by explaining local disk saving behavior and the temporary signed URL mode with a validity window, going beyond what annotations provide.

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?

The description is a single compact sentence that packs in both main functionality and a key edge case (link_only). It is front-loaded with the action and resource, with no wasted 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?

The tool has good annotations, full schema coverage, and an output schema. The description covers the two primary modes of operation and the temporary URL timeout, which is sufficient for an agent to select and invoke it correctly. Minor gaps like overlapping item_id/version_id usage are already evident from the schema.

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%, so the baseline is 3. The description adds value by explaining the link_only parameter's behavior (returns a temporary URL) and referencing the dest_path as 'local disk', which goes beyond the schema descriptions.

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 tool downloads a document from ACC Docs to local disk or returns a temporary signed URL. This is a specific verb+resource pairing that distinguishes it from siblings like acc_upload_file or acc_copy_file.

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 implies usage (use this to download files), but it doesn't explicitly state when to use this versus alternatives or mention any exclusions. Context from sibling names helps but isn't spelled out in the description.

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