polynodes_granular_duration

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 safety profile is covered structurally. The description adds only 'Returns: JSON confirmation,' which is redundant given an output schema exists, and says nothing about this being a real-time audio parameter change with immediate audible effect.

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 definition is short and front-loads the core action, which is good, but the 'Args: params: value.' and 'Returns: JSON confirmation.' lines are pure boilerplate that consume space without adding information.

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 live audio parameter setter among 40+ similar siblings, the description should at least say what the number measures and how it interacts with the granular switch. It omits everything beyond the range, and while an output schema exists, the one genuinely useful disclosure (real-time sound modification) is absent.

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?

With schema description coverage reported at 0% and only one nested object parameter, the description carries the load but offers almost nothing: 'params: value.' is boilerplate that adds no meaning, and the 10-1000 range merely repeats the schema's own minimum/maximum. Units and the effect of the duration value on granular playback are never stated.

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 and resource ('Set granular chunk duration') with the valid range (10-1000), so an agent can distinguish it from unrelated siblings like polynodes_set_gain. However, it does not differentiate itself from close siblings polynodes_granular_duration_mod_range or polynodes_granular_switch, leaving ambiguity about which granular parameter is being set.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer a sibling such as the mod-range variant. The only implied context is that this belongs to a granular synth section, which the agent must infer from the name alone.

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