Add title / text

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

No annotations provided, but description discloses non-destructive addition of a title element. However, it lacks details on results or potential conflicts, which is acceptable for a simple additive tool.

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?

Three sentences: first defines the action, second gives placement tip, third notes default and optional param. Efficient and front-loaded, with no unnecessary words.

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?

For a simple tool with 5 parameters fully documented in schema, the description provides key behavioral context. Lacks mention of return value, but not critical given no output schema.

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 coverage is 100%, so baseline is 3. Description adds minor context about videoTrack placement and durationSeconds being optional, but no significant extra meaning for other parameters.

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 clearly states the tool adds an animated title using .mogrt templates with a default Basic Title, distinguishing it from sibling tools like premiere_add_overlay or premiere_add_effect.

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 provides guidance to place on a video track above footage, implying usage for adding titles. It does not explicitly exclude alternatives but context differentiates it from other tools.

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