download_my_caption

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

No annotations are provided, so the description carries the behavioral burden. It discloses a critical restriction (only works for owned videos) and indicates the output format. It does not detail failure modes or the exact response envelope, but for a simple download tool this is adequate and goes beyond the schema.

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 with no fluff. The core action is front-loaded, the ownership constraint is stated clearly, and the alternative tool is referenced in the second half. Every word earns its place.

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?

With one required parameter, a format enum, and no output schema, the description provides enough: purpose, scope limitation, output formats, and the correct alternative when the ownership condition fails. An agent can invoke this tool correctly without needing more context.

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 50%; only caption_id is described in the schema, while format has an enum and default. The description mentions SRT/VTT, mirroring the enum, but adds no new parameter-level meaning beyond what the schema already provides.

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 ('Download'), a resource ('official caption track'), and the output formats ('SRT or VTT'). It also explicitly distinguishes itself from get_transcript by naming the ownership restriction, making the tool's purpose unmistakable.

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?

It says exactly when to use this tool versus the alternative: 'Only works for videos owned by the signed-in account — use get_transcript for anything else.' This is an explicit conditional with a named sibling, leaving no ambiguity for an agent.

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