transport_toggle_metronome

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states that the operation is a state toggle rather than a read-only query or destructive reset. It does not mention whether the new state is returned, but for a zero-argument transport toggle this is a minor omission rather than a meaningful gap.

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 entire description is 'Toggle metronome on/off.' — a single front-loaded sentence with no filler, redundancy, or unnecessary detail. Every word contributes to the agent's understanding.

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 parameterless tool with no output schema, this description is sufficient for an agent to select and invoke it correctly. The sibling list adds no missing context, because no sibling tool overlaps with metronome control.

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 input schema has zero properties and 100% coverage, so there are no parameter semantics needing explanation. The baseline of 4 applies because the description correctly does not invent or omit parameter guidance where none is 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?

The description uses a specific verb ('Toggle') and a specific resource ('metronome'), making the action unambiguous. It is distinguishable from every sibling tool, including other transport toggles, because no other tool in the list targets the metronome.

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 usage is implied: an agent should call this when it wants to flip the metronome state between on and off. However, the description does not explicitly state when to use it versus alternatives, mention prerequisites, or note any conditions such as requiring an open project.

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