insert_title

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

No annotations are provided, so the description must fully disclose behavior. It mentions insertion at the playhead and the fusion parameter effect, but does not address prerequisites (e.g., active timeline), side effects (e.g., overwriting), or error conditions. This is insufficient for a tool with no annotations.

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 very short—one sentence plus a note—and front-loads the main action. However, it could be better structured (e.g., separating mandatory and optional parameters). 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?

Given no output schema and no annotations, the description lacks critical context: prerequisites (active timeline), return value, error behavior, and typical use case. For a tool with two parameters, it leaves significant gaps.

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 0%, placing full burden on description. The 'fusion' parameter is explained inline, but the required 'name' parameter is not described at all. The description adds minimal value beyond the parameter names.

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 'Insert a title at the playhead' with a specific action and resource. It also distinguishes standard titles from Fusion titles via the 'fusion' parameter, setting it apart from sibling tools like 'insert_generator' and 'insert_fusion_composition'.

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?

The description implies usage context (standard vs Fusion title) but does not explicitly direct when to use this tool versus alternatives like 'insert_generator' or 'insert_fusion_composition'. No when-not-to-use guidance is provided.

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