speechify_download_file

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

With no annotations, the description carries the full burden; 'atomically' is a genuine behavioral disclosure (no partial files) that the schema cannot express. However, it omits permissions/auth needs, what happens when the target path already exists and overwrite is false, and whether any side effects occur on the remote item.

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?

A single front-loaded sentence with no filler; the destination constraint, which is the most error-prone part of the call, is stated first.

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?

No output schema and no annotations mean the description must explain the write side effects and result, but it does not say what is returned or how failure/overwrite conflicts are reported. For a tool that writes to the local filesystem, that is a material gap.

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 0%, so the schema only gives types; the description partially compensates by clarifying that output_path is an absolute local path. It says nothing about item_id (what identifier domain it belongs to) or about overwrite semantics, leaving two of three parameters without added meaning.

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?

States a specific verb ('Download') and resource ('one file') plus the destination constraint ('local absolute output path'), which separates it from metadata-reading siblings like speechify_get_item. It stops short of naming a sibling or explaining what 'one file' means relative to the other item 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?

There is no statement of when to use this tool versus speechify_get_item or the other item tools, and no prerequisites such as needing the item to be fully processed (e.g., a completed job) before download. The word 'atomically' implies a safe write but does not tell the agent when this is the right call.

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