effect_adjustable_fade

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

With no annotations provided, the description carries the full disclosure burden. While it explains curve behavior (exponential/logarithmic), it omits critical operational context: whether the effect is destructive, requires a selection, or how it handles edge cases.

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 efficiently structured with a single purpose sentence followed by an Args block. No words are wasted, though the Args documentation format is slightly informal relative to typical schema-centric descriptions.

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?

The description adequately covers the parameter semantics but lacks operational completeness for an audio effect tool. It omits whether the tool modifies audio in-place, requires a time selection, or returns status information.

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?

Given 0% schema description coverage (only titles present), the description excellently compensates by fully documenting both parameters: fade_type enumerates the 0/1 values with meanings and default, and curve explains the numeric range interpretation (positive/negative) and default.

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 an 'adjustable fade with curve control,' specifying the verb and resource. However, it fails to explicitly distinguish this from siblings like effect_fade_in and effect_fade_out, which this tool likely generalizes.

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 no guidance on when to use this tool versus the simpler effect_fade_in/out alternatives, nor does it mention prerequisites like requiring an audio selection before application.

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