download-caption

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

With no annotations provided, the description carries the full burden. It does disclose a behavioral trait—costing 200 quota units—which is absent from the schema. However, it omits other behavioral details such as file overwrite behavior, permission requirements, and return value, leaving significant gaps.

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 concise two-clause sentence with all necessary core information front-loaded. Every word contributes to understanding the action and a key cost implication, with no 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?

The tool has four parameters, no output schema, and no annotations, but the description provides only the essential action and cost. Missing contextual details include how to obtain a captionId, expected return behavior, and potential side effects (e.g., overwriting files). This is not fully complete for a tool with these gaps.

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 the parameters (captionId, outputPath, format, language) are already well documented. The description adds minimal semantic value beyond reinforcing that outputPath is a local file path; no new meaning is added for format or language.

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 states a specific verb and resource ('Download a caption track') with a clear destination ('to a local file path'). It also includes a cost factor, making it distinct from sibling caption tools like list-captions, upload-caption, update-caption, and delete-caption.

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?

No guidance is provided on when to use this tool versus alternatives, such as first calling list-captions to obtain a captionId. There are no exclusions, prerequisites, or alternative tool mentions. The cost statement is informational but does not clarify usage context.

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