Read the speed masters, what follows them, and the sound input

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

With no annotations, the description carries the full burden and does well: it declares the tool read-only, states that beat detection and lock are not readable on 2.5.1 and that synchronisation is therefore never claimed, and notes duplicate names make links ambiguous. This version-specific limitation disclosure is genuinely useful, though it does not cover auth requirements or result volume.

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?

Front-loads the read-only nature and the resource, and each sentence carries distinct content. It is a dense wall of text with long compound sentences, which slightly hurts scannability, but nothing is padding given the schema coverage gap it must fill.

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?

With no output schema, the description fully explains the return contents for the base read, the usage expansion, the sound expansion, and the observe behavior, plus the 2.5.1 readability limits. An agent has enough to call it and interpret the response without further documentation.

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 only 25% (only 'masters' is documented), so the description must compensate and it does thoroughly: it defines usage (per-master followers by speed and by rate, plus executors), sound (device, available devices, SoundIn level, master 16 driven by input), and observe_seconds (sampling behavior and default of master 16). Each parameter's meaning and default is spelled out beyond the schema.

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?

Opens with a specific verb and resource ("Read-only. The 16 speed masters") and enumerates exactly what is retrieved (name, fader, base BPM, speed scale, effective BPM, tempo text, learn, lock, problems). It explicitly distinguishes itself from timing masters (pool 5) and cue timing, so an agent can route without opening a sibling schema.

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?

Gives clear conditions for the optional parameters (usage default true, sound default true, observe_seconds 0-10) and names the conceptual alternatives (timing masters, cue timing). It does not explicitly contrast with the adjacent write/read siblings like configure_speed_master, speed_master_action, or observe_tempo, so a small routing gap remains.

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