Stop peak watch + diagnose (Mix Doctor)

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

Annotations already declare readOnlyHint=true and idempotentHint=true; description adds that it is read-only and proposes fixes but applies nothing, plus distinguishes full-song analysis from the ~1.2s snapshot. Provides meaningful behavioral context beyond annotations.

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 sentences, no wasted words, front-loaded with core action. Every sentence is informative and necessary.

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 tool with no parameters, existing annotations, and an output schema, the description is complete. It explains the scope (full-song vs snapshot), read-only nature, and what it produces (clipping/headroom/imbalance diagnosis).

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?

No parameters in input schema, so schema coverage is 100%. Baseline for 0 params is 4; description adds no further parameter info needed.

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?

Clearly states it stops the peak watch and performs diagnosis on full-song running-max peaks. The verb 'stop' and resource 'peak watch + diagnose' are specific and distinct from sibling tools like fl_mix_watch_start and fl_mix_watch_status.

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?

Implied usage after starting a watch via fl_mix_watch_start, but no explicit when-not-to-use or alternative tools mentioned. Sibling tool list provides context but description lacks direct guidance.

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