Add text overlay

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

No annotations are provided, so the description alone must disclose behavioral traits. It only states 'adds' without mentioning side effects, permissions, or what happens if the draft doesn't exist. No info on idempotency, track creation, or response behavior.

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?

Description is a single, front-loaded sentence with no filler. It is concise but could be expanded slightly to improve completeness without being verbose.

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?

Given 10 parameters, no output schema, and no annotations, the description is insufficient. It does not specify required context (e.g., draft must exist), ordering, or the nature of the text overlay on the timeline. Completeness is inadequate for accurate tool selection.

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 covers all 10 parameters, so baseline is 3. The description adds no additional parameter semantics beyond the schema. It does not explain parameter relationships or defaults beyond what's in the schema.

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?

Description clearly states it adds a text overlay to a draft text track. The verb 'adds' and resource 'text overlay' are specific. It distinguishes from sibling tools like add_audio or add_image, though it could be more precise about what constitutes a text overlay.

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 on when to use this tool versus alternatives like add_image or add_video. Implied usage is for adding text, but no explicit when-not or prerequisites (e.g., draft must exist). Sibling tools are listed but not referenced.

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