transport_toggle_metronome

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

The description accurately reflects the action of toggling, but does not disclose any additional behavioral traits such as whether playback continues, if there is a visible indicator, or any side effects. Since annotations are absent, the description carries the full burden but provides minimal extra value.

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 at two words, front-loading the essential action and resource. Every word is necessary, and there is no extraneous 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?

For a simple toggle with no parameters and no output schema, the description is minimally adequate. It conveys the core action but lacks details about the effect on the system or any visual/audio feedback. A more complete description could help the agent understand the tool's impact.

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?

The tool has no parameters, so the description does not need to add parameter-level meaning. With zero parameters, a baseline of 4 is appropriate per the guidelines.

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 action (toggle) and the resource (metronome), making it easy for an agent to understand what the tool does. It distinguishes itself from siblings like transport_play or transport_stop, which handle playback rather than metronome state.

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. The description does not mention prerequisites, typical use cases, or when toggling the metronome is appropriate, leaving the agent without context for decision-making.

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