effect_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 burden of behavioral disclosure. It states that the tool applies a fade-out and requires a selection, but it does not mention whether the operation is destructive, reversible, or what actually happens to the audio beyond 'fade-out.' For a mutation tool, this leaves important behavior undisclosed.

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?

Two short sentences: one states the action, one states the required precondition. There is no filler, and the essential usage requirement is included.

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 with no output schema, the description is mostly complete: it says what the tool does and what must be done first. It lacks explicit safety or reversibility guidance, but the operation is simple enough that this is a minor gap.

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?

This tool has no parameters, so there is nothing for the schema to document. The description appropriately refers to the selection prerequisite instead, which is the meaningful input the agent needs to understand.

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 a specific action and resource: 'Apply a fade-out to the selected audio.' It distinguishes the tool from fade-in by direction, though it does not explicitly differentiate it from similar sibling tools like effect_studio_fade_out or effect_adjustable_fade.

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 an explicit prerequisite: 'Select the region to fade first.' This gives usable context for when to use the tool, but it does not mention alternatives, when not to use it, or how it compares to other fade-related tools.

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