fmod_Sound_setFadeOutCurve

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

No annotations are present, so the description must disclose behavioral traits. It does not mention whether the curve overwrites existing settings, if the sound must be stopped, or any side effects. The minimal description fails to provide critical behavioral context.

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 extremely concise: a single sentence plus a markdown reference. Every word is functional, and the structure is front-loaded with the main action. No wasted text.

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 the tool is simple (3 parameters, no nested objects, no output schema), the description is minimally adequate. However, it does not mention return values (e.g., void or success flag) or any preconditions, leaving room for improvement.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema: it clarifies 'length' as duration and 'curveShape' as velocity with values explained, but this largely repeats the schema. No additional meaning is provided.

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 sets the fade-out curve with specified length and shape, using a verb+resource pattern. However, it mentions 'instrument' while the tool name refers to 'Sound', introducing slight ambiguity. It does not explicitly distinguish from the sibling tool fmod_Sound_setFadeInCurve.

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?

No guidance is provided on when to use this tool versus alternatives like the fade-in curve setter. The description lacks context for prerequisites, timing, or conflicts with other operations.

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