list_clip_effects

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'list' implies a non-mutating read, but the description does not say whether output is a simple list, what properties are included, which clip is inspected, or whether any implicit selection is required.

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 short and front-loaded, but most of its content restates the tool name and 'Premiere Pro expanzed operation' is boilerplate. It is concise in length but not in information density.

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 zero-parameter tool, the description must explain the implicit state it uses, such as the currently selected clip, and what the returned effect list will look like. It does neither, and it provides no disambiguation against the many effect-related sibling tools.

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 tool has zero declared parameters and the schema coverage is 100%, so there are no parameters for the description to document. The 0-param baseline of 4 applies; the only wrinkle is additionalProperties:true, which the description does not need to explain.

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 a specific action, 'list', and a resource, 'clip effects', so an agent can infer the basic operation. However, it does not distinguish this from the sibling 'list_available_effects' and the phrase 'expanded operation' adds ambiguity rather than clarity.

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?

There is no guidance about when to use this tool, what implicit context it relies on, or which alternative to prefer. An agent cannot tell from the description when to call list_clip_effects versus list_available_effects or get_effect_properties.

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