effect_fade_in

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

No annotations provided, so description carries full burden. Mentions 'selected audio' implying state dependency, but fails to disclose destructive mutation nature, fade curve characteristics, or reversibility of the operation. Minimal viable disclosure for an audio 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 with zero waste. Front-loaded with the action ('Apply a fade-in'), followed by prerequisite. Every word earns its place.

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 fade effect with no parameters or output schema, the description covers basic operation and selection prerequisite. However, gaps remain regarding fade duration behavior (does it use full selection length?), curve type, and destructive side effects.

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?

Zero parameters per schema, establishing baseline of 4. Description adds critical implicit context that the tool operates on the 'selected' region, compensating for the empty parameter schema by explaining the selection dependency.

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?

Description uses specific verb 'Apply' with resource 'fade-in' and target 'selected audio'. Clearly distinguishes from sibling tools like effect_fade_out and effect_crossfade_clips by specifying the exact fade direction.

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?

Provides clear prerequisite instruction 'Select the region to fade first', indicating this tool requires a prior selection action. Lacks explicit comparison to alternatives (e.g., when to use fade_in vs fade_out), but the prerequisite guidance is valuable.

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