fusion_comp_add

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

No annotations provided. Description lacks details about side effects, failures, permanent changes, or required permissions. It only states the action and return value without behavioral disclosure.

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?

Extremely concise single sentence. Front-loaded with verb and resource. However, it sacrifices necessary detail, but for conciseness it scores high.

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 the complexity (similar siblings, one parameter, no output schema), the description is too brief. It does not explain what a 'Fusion comp' is, how the returned name is used, or what input is needed. Incomplete for safe invocation.

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 only parameter 'item_handle' is not explained. The description mentions adding a comp to a 'timeline clip' but does not clarify that 'item_handle' likely refers to a clip or timeline item. With 0% schema coverage, the description should compensate but fails to.

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 states 'Add a Fusion comp to a timeline clip and return its name' but is ambiguous: does it add an effect to an existing clip or create a new fusion clip? It does not distinguish from siblings like 'fusion_clip_create' or '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?

No guidance on when to use this tool versus alternatives. No prerequisites or context provided (e.g., need a selected clip or timeline).

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