add_text_overlay

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

No annotations provided, so the description must disclose side effects and nuances. It does: duration is 'best-effort' (may not be exact), the override field behavior is explained (ignores extra text fields, fails if property not found), and the rollback via rollbackOnAllFail. These add valuable behavioral context beyond the raw 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?

Description is two sentences: the first states the core action and the requirement; the second explains the field mapping and a caveat. Concise and front-loaded, but could be slightly more structured (e.g., bullet points) for readability. Still, every sentence adds value.

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?

Covers the critical requirement (MOGRT path), the multi-field mapping, the best-effort duration behavior, and the override mechanism. It lacks explicit error handling (e.g., what happens if the MOGRT is invalid) but provides enough for an agent to use the tool correctly. Given no annotations or output schema, it is reasonably complete.

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 already describes each parameter well (e.g., duration is 'best-effort', trackIndex mentions creating track first). The description adds the mapping of text fields to MOGRT components, which is not fully in schema (schema only says 'typically the main title' for text). It also clarifies the override behavior. The description adds meaning beyond the schema, especially the component behavior and the text2/text3/text4 mapping.

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?

Clear verb+resource: 'Adds a text overlay' to the video timeline. Distinguishes itself from sibling tools by specifying the MOGRT requirement and the up-to-4 text fields, which is unique among the many set_* and add_* tools. The purpose is 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?

States when to use: requires a .mogrt template, and the description explicitly mentions using add_track first if needed (via schema). It also clarifies when to use the override property (when auto-detection fails), providing alternative behavior. However, it doesn't explicitly list sibling alternatives or exclusions, but the usage context is clear.

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