get_fusion_comp_list

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 only states it gets compositions, but does not mention that it is read-only, what happens if no comps exist, whether it returns full details or just names, or any side effects. This is minimal disclosure 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 concise: two sentences. However, it could be better structured with a clearer separation of purpose and parameters. It lacks front-loading of critical info like return type.

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 list tool with an output schema (likely covering return format), the description is adequate but leaves gaps. It does not specify what a 'Fusion composition' object contains or behavior in edge cases. Given the output schema exists, a score of 3 is appropriate.

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%, so the description must compensate. It groups the three parameters as 'Clip locator', which adds some meaning, but it does not explain each parameter individually (e.g., valid values for track_type, meaning of index defaults). The added value is minimal.

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 it retrieves all Fusion compositions for a timeline item. It uses a specific verb 'Get', identifies the resource 'Fusion compositions', and the scope 'associated with a timeline item'. This distinguishes it from sibling tools like add_fusion_comp (adds) or delete_fusion_comp (deletes).

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. There is no mention of when not to use it, prerequisites, or comparisons with similar tools like get_timeline_items or get_fusion_comp (if it exists). The description only states what it does without context.

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