effect_fade_in

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

The description states it applies a fade-in to selected audio, indicating a mutation. It does not disclose whether it is destructive, reversible, or any side effects, but given no annotations, it carries the burden. For a simple effect, the behavior is mostly transparent.

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 fluff, front-loading the action and the prerequisite.

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?

Given it has no parameters, no output schema, and simple behavior, the description is complete. It tells what it does and the prerequisite, enough for an agent to call it 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?

There are no parameters, so the description doesn't need to explain any. The schema coverage is 100% trivially, so the baseline of 4 applies.

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 a fade-in to the selected audio, using a specific verb and resource. It distinguishes from sibling effect_fade_out by specifying fade-in. The prerequisite about selecting the region further clarifies the target.

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?

It explicitly instructs to select the region before applying, which is a direct usage guideline. However, it does not mention when not to use this tool or suggest alternatives, but for a simple effect this is sufficient.

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