apply_effect

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

It mentions verification of parameter readbacks and identification of the created component, which provides some behavioral detail. However, it omits side effects such as undo behavior, error cases, or project mutation semantics.

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 concise sentence without unnecessary fluff, but it lacks structured formatting such as bullet points or examples, and does not reference the schema fields.

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?

Without annotations, the description provides moderate context about the tool's behavior but misses prerequisites, side effects, and typical use cases. It also does not cross-reference related 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?

Parameter descriptions are minimal: 'The ID of the clip' and 'The name of the effect' are clear, but the 'parameters' object lacks structure or examples, and the exact keys and value types are not specified.

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 (applies a visual or audio effect) and the specific outcomes (identifies the exact newly created component and verifies parameter readbacks), distinguishing it from simpler apply-effect tools.

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 implies usage (applying an effect to a clip) but does not explicitly mention when to choose alternative tools like batch_apply_effect or list_available_effects, nor does it specify limitations.

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