effect_paulstretch

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

No annotations are provided, so the description carries the full burden. It mentions 'extreme time-stretch' but does not disclose whether the effect is destructive, whether it creates a new clip, or any performance implications. This is a significant gap for a mutation tool.

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 concise: two sentences for purpose and a bullet list for parameters. It is front-loaded with the key action and efficient with no wasted words.

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 effect with two parameters and no output schema, the description covers purpose, prerequisite, and parameters. It is mostly complete but could mention whether the effect replaces the selection or creates a new clip.

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 description explains both parameters (stretch_factor and time_resolution) with their defaults and units, adding meaning beyond the schema titles. Schema coverage is 0%, so this explanation is essential. However, it lacks typical ranges or usage tips.

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 tool applies an 'Extreme time-stretch effect' that 'creates ambient/drone textures', distinguishing it from other effects like reverb or echo. The verb 'time-stretch' and resource 'audio' are precisely identified.

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 notes 'Select audio first' as a prerequisite but does not provide guidance on when to use this effect versus alternatives like effect_sliding_stretch or when not to use it. No explicit context or exclusions are given.

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