polynodes_set_playback_rate

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the mutation/idempotency profile is covered externally. The description adds the value constraints (0.3-10 / 0.3-20 / 0.3-30 per granularity level), which is useful, but says nothing about units (is 1.0 normal speed?), clamping behavior out of range, or whether the rate is a multiplier or a tempo-relative setting.

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-loaded with the action and the key range constraints, then structured Args/Returns. The 'Returns: JSON confirmation' line is nearly content-free, but the overall text is tight with little waste.

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?

An output schema exists, so the return value need not be explained. Still missing for a mutation tool with openWorldHint: what 'value' means physically (multiplier vs ratio vs semitones) and how out-of-range input is handled. Adequate but with clear gaps.

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 reported at 0%, so the description must carry the parameter burden, and it does partially: it names the two subfields (level, value) and maps each level to its numeric range. However, it adds no interpretation of the value (units, min/max semantics, what happens out of range), so it only partly compensates.

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 playback rate for agents') and adds per-level range detail, so the intent is immediately clear. It does not explicitly distinguish itself from the very similarly named sibling polynodes_set_playback_rate_mod_range, so an agent must infer which one applies.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer. The near-identical name polynodes_set_playback_rate_mod_range makes this omission costly, since the agent gets no routing guidance between the two.

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