effect_studio_fade_out

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

There are no annotations, so the description carries the full behavioral disclosure burden. It clearly says the tool applies a fade-out to the selected audio and takes no parameters, but it does not mention whether the change is destructive, whether a selection is strictly required, or how the output is represented. This is adequate for a simple effect tool but leaves some behavioral traits implicit.

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 two sentences with no wasted words. It front-loads the action and target, includes the key comparison to a sibling, and states the parameter behavior cleanly.

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 effect with no output schema, the description covers the essential information: what the tool does, what it acts on, how it differs from the closest sibling, and the fact that no parameters are needed. Nothing critical is missing.

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 schema has zero parameters, and the description reinforces this by explicitly stating 'Takes no parameters.' Since there are no parameters to document, the description adds appropriate clarity beyond the empty schema.

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 verb ('Apply'), a clear resource ('a fade-out to the selected audio'), and explicitly distinguishes itself from the sibling effect_fade_out ('smoother, more natural'). It also notes it takes no parameters, which makes the purpose unmistakable.

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 directly names effect_fade_out as the alternative and explains why to prefer this tool: it is smoother and more natural. It does not mention other fade-related siblings or provide explicit 'when not to use' guidance, but the context is clear enough for an agent to select it appropriately.

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