find_spectrum_peaks

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

Annotations give readOnlyHint=false but do not explain why. The description closes that gap by disclosing 'temporarily pauses readout', which tells the agent this has a transient side effect on the instrument and is not a pure read. It stops short of saying when readout resumes or whether the pause is bounded.

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?

A single tight sentence with the action front-loaded and the side effect appended, with no filler. It is appropriately sized, though the appended clause could be expanded slightly without harming flow.

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?

An output schema exists so return values need not be explained, and the pausing behavior is disclosed. However, with zero parameter documentation and no usage guidance against a crowded sibling set, the definition is only minimally sufficient.

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 0% and the description names no parameter (limit, min_level_dbm, min_separation_hz). 'Strongest' and 'sampled' only loosely gesture at level filtering and the limit, leaving all three parameters' meaning to be guessed from their names.

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?

States a specific verb (find) and resource (spectrum peaks), plus the scope of 'snapshot current trace' and 'strongest sampled local maxima'. This distinguishes it reasonably from capture_spectrum/scan_spectrum, though it never explicitly names those siblings.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives like capture_spectrum or scan_spectrum. The agent must infer from context alone when peaks should be found versus a raw capture taken.

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