effect_fade_in

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

With no annotations, the description must carry behavioral disclosure. It communicates that the tool mutates audio by applying a fade-in and requires a selection, but it does not mention reversibility, whether the original audio is replaced, or any default fade behavior. These gaps are modest for a well-known effect.

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, each earning its place: one states the operation, the other states the required precondition. No redundant wording or unnecessary detail.

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 parameterless audio effect with no output schema, this is complete. It explains what happens, what scope is affected, and what must be done first. There is no missing information an agent needs to invoke 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?

The tool takes zero parameters, so the description does not need to document anything beyond the operation itself. The baseline of 4 applies here since there are no parameters whose meaning could be clarified.

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 fade-in') and resource ('selected audio'), making the tool's purpose unmistakable. It also distinguishes this from related effect tools by naming the exact operation rather than a generic 'apply effect' phrase.

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 gives clear operational context: the user must select the audio region before invoking the tool. It does not explicitly name alternatives like effect_fade_out or effect_adjustable_fade, but the prerequisite is enough to tell the agent when this tool is appropriate.

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