tidal_set_tempo

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

With no annotations, the description carries the full burden, and it does disclose the interpretational model (four beats per cycle, setcps (bpm/60/4)). However it says nothing about whether the change applies live to currently playing patterns, persistence, or any session requirements.

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 economical sentence with the core action front-loaded and no filler. The parenthetical formula is arguably dense but earns its place by clarifying units.

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 trivial one-parameter setter with no output schema and no annotations, the description covers the action, unit, and semantics adequately. Only the missing sibling routing context keeps it from being fully complete.

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 coverage is 100% and the bpm parameter is already documented in the schema with its 20-999 range. The description adds the beat-cycle interpretation, but that meaning is marginal beyond what the schema provides.

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+resource ('Set the tempo in beats per minute') and even exposes the underlying conversion, so the action is unambiguous. It does not differentiate itself from the sibling strudel_set_tempo, which is the main gap.

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 versus alternatives like strudel_set_tempo or tidal_set_control, and no prerequisites or context about a running session. The agent must infer usage entirely.

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