set_groove_amount

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

No annotations are provided, and the description only restates the action without disclosing side effects, persistence, or prerequisites. It does not describe what happens when the amount changes or any related state.

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?

Extremely concise: a clear one-line action and a minimal Args section. Every sentence contributes essential information, with no 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?

For a simple one-parameter setter, the description covers the action and parameter range adequately. An output schema exists, so return values need not be described. Lacks only broader context about when to apply the global groove, but this is a minor gap given the tool's simplicity.

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?

The description adds a meaningful range (0.0 to 1.0) for the amount parameter, which is not present in the schema. This compensates for the 0% schema description coverage, though it does not explain behavior on out-of-range values.

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?

Clearly states it sets the global groove amount, with a specific verb and resource. This distinguishes it from sibling tools like set_clip_groove and set_groove_property.

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?

The term 'global' implies project-wide scope, but there is no explicit guidance on when to use this tool versus alternatives such as set_groove_property or set_clip_groove. Usage context is only implied.

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