add_title

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

No annotations provided, so the description must fully disclose behavior. It mentions insertion at the playhead, which is a key behavioral detail. However, it omits whether the operation is destructive (e.g., overwrites existing clips) or requires any permissions. The behavioral transparency is adequate for a simple insertion but lacks completeness.

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 single, well-structured sentence that front-loads the action ('Insert') and key details. No unnecessary words, earning its place. Slightly penalized for not immediately clarifying the parameter's role.

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 one parameter and no output schema, the description covers the essential: what it does and where. It does not mention prerequisite conditions (e.g., timeline open), but given the simplicity, this is a minor gap. Overall, 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?

The single parameter 'text_or_title' has no schema description (0% coverage). The tool description adds meaning by giving examples ('Text', 'Text+'), indicating it controls the type of title generator. This is helpful but could be more explicit about the allowed values or format.

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 action ('insert') and resource ('title generator') with examples ('Text', 'Text+'). It specifies location ('at the playhead of the current timeline'). However, it does not differentiate from sibling tools like add_fusion_title or add_generator, which could cause ambiguity.

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. Does not state prerequisites (e.g., an open timeline), nor when not to use it. The description is purely functional without contextual usage hints.

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