list_transitions

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

With no annotations, the description must indicate this is a safe read-only operation. The verb 'List' implies no modification, and 'every' conveys completeness of the returned set. It does not explicitly mention side effects, but for a simple enumeration no side effects are expected.

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, front-loaded sentence with no filler. It delivers the essential scope and purpose without redundancy.

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 tool with one optional parameter and no output schema, the description is adequately complete. It specifies the result as 'every video transition name', which implies an array of strings, and references add_transition for usage context. It could have been more explicit about the return format, but this is a minor gap.

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% since the filter parameter is fully described as a 'Case-insensitive substring'. The description adds no extra parameter detail, but the high schema coverage makes 3 the appropriate baseline.

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 ('List') and the resource ('every video transition name Premiere can apply'). It also explicitly connects to a sibling tool ('for use with add_transition'), which distinguishes it from similar enumeration tools like list_effects.

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 states the intended downstream use ('for use with add_transition') and implies it is a lookup tool for transitions. However, it does not explicitly contrast with alternatives or state when not to use it, so slightly below the top score.

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