list_available_effects

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

The verb 'Lists' implies a read-only operation, but the description does not explicitly state side effects or behavioral details such as output format, sort order, or inclusion of third-party effects. Since no annotations are provided, the description carries the full burden but adds minimal transparency beyond the core purpose.

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, clearly worded sentence that immediately states the tool's function. There is no wasted content, and the essential information is front-loaded.

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, parameterless list tool with no output schema, the description 'Lists all available video effects in Premiere Pro' fully conveys the tool's purpose and expected return. It is sufficient for an agent to select and invoke the tool correctly.

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 parameters, as indicated by the empty input schema. According to the baseline rule for 0 params, the description is not expected to explain parameter behavior, so a score of 4 is appropriate.

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 uses a specific verb 'Lists' and a specific resource 'all available video effects' with context 'in Premiere Pro'. This clearly distinguishes it from sibling tools like list_available_audio_effects and list_available_transitions by explicitly limiting to video 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or alternative tools. The usage is only implied by the tool's name and the generic description, not explicitly stated.

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