set_metronome

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

The description aligns with the annotation (destructiveHint: false) and indicates a toggle behavior, but adds no extra context about side effects (e.g., whether play must be on, or impact on performance).

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 a single, efficient sentence with no wasted words, perfectly sized for a simple toggle action.

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 tool's simplicity (one boolean parameter, non-destructive, output schema exists), the description is nearly complete, though mentioning the metronome's state after toggling could add slight clarity.

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 single boolean parameter 'enabled' is not explained in the description; with 0% schema description coverage, the agent must infer its meaning from the tool name and context, which is acceptable for a boolean but lacks explicit guidance.

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 ('Turn on/off') and the resource ('Live's metronome click'), making the tool's purpose unambiguous and distinct from sibling set_* tools.

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 provides no guidance on when to use this tool versus alternatives, nor does it specify any prerequisites or context for using the metronome toggle.

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