set_metronome

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

With no annotations provided, the description bears full burden for behavioral disclosure. It only states the action but does not mention side effects, such as whether turning the metronome affects playback or visual indicators. The required 'ctx' parameter is not explained, leaving ambiguity about how context is used.

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 (7 words), which is good for readability but sacrifices necessary details. It is front-loaded, but the brevity leaves gaps in purpose, parameters, and context. A slightly longer description could improve clarity without losing conciseness.

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 boolean setter with no output schema, the description is minimally adequate. However, given the lack of annotations and 0% schema coverage, it should mention checking current state via 'get_metronome' or explain the context parameter. The tool's simplicity does not fully excuse the missing details.

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 tool description adds no explanation for the parameters. It does not clarify what 'on' means (true=on, false=off?) or address the 'ctx' parameter at all. The agent must infer parameter meaning solely from names and types.

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's purpose: to turn the metronome on or off. It uses a specific verb+resource ('turn the metronome') and distinguishes from sibling tool 'get_metronome' which likely retrieves the current 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 on when to use this tool or when not. Does not mention that 'get_metronome' can be used to check the current state before toggling, or any prerequisites like playback context. The agent is left 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.