AudacityMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions 'selected audio' implying a selection requirement, it fails to clarify whether the effect is destructive (modifies in-place), what happens if no audio is selected, or details about the processing behavior beyond the parameter definitions.

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 clear purpose statement followed by an 'Args:' section documenting parameters. Every sentence serves a function; there is no redundant or extraneous 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?

For a two-parameter audio effect tool without output schema, the description adequately covers the parameter semantics and basic purpose. However, it lacks usage context (when to prefer echo over reverb) and operational details (error handling, selection requirements) that would make it complete.

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, the description fully compensates by documenting both parameters with types ('seconds', 'factor'), valid ranges ('0-1'), semantic meaning ('lower = faster decay'), and default values ('Default: 0.5') for each.

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 specific action ('Apply echo effect') and target ('selected audio'), distinguishing it from sibling tools like effect_reverb or effect_phaser through the specific 'echo' terminology.

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 alternatives (e.g., effect_reverb for reverberation), nor does it mention prerequisites such as requiring an active audio selection before invocation.

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