Start full-song peak watch (Mix Doctor)

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

The description notes 'Read-only' aligning with the readOnlyHint annotation, and explains the continuous sampling behavior. It adds user guidance beyond annotations, though it could detail more about the running max update.

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 two concise sentences, front-loaded with the action and key details. Every word serves a purpose, with no unnecessary information.

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 output schema exists, the description sufficiently covers purpose and usage context. It is complete for a simple command, though it could mention the return value briefly.

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 coverage is 100% with detailed parameter info (interval_ms with default, min, max). The description does not add extra meaning beyond the schema, so baseline score of 3 applies.

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 begins a peak-HOLD watch, continuously sampling mixer track peaks until stopped. It uses specific verbs and resources, distinguishing it from sibling tools like fl_mix_watch_stop 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?

The description instructs the user to play the song while the watch runs, then stop for accurate level diagnosis. It implies when to use the tool, though it does not explicitly mention when not to use or alternative tools.

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