set_groove_property

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

No annotations are present, so the description carries the full burden. It clearly indicates a mutation ('set') and specifies valid ranges/mappings for values. However, it does not disclose potential side effects, reversibility, or impact on clips using the groove. Missing context about return behavior, though 'set' implies a write operation.

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 description is a compact docstring with a clear first line and an Args block. Every line adds necessary value, with no redundancy or fluff.

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 setter, the description covers parameter semantics thoroughly. It lacks some broader context (e.g., prerequisites, side effects, error conditions), but given the output schema exists and the tool is straightforward, it is reasonably complete. More explicit mention of what the groove is and how it ties to the pool would improve it.

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 fully documents all three parameters with exact allowed values, including a mapping for base values and range for amounts. This goes far beyond the schema's bare types and is essential since schema coverage is 0%.

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?

The description uses a specific verb ('Set') and resource ('property on a groove'), and clarifies that the groove is in the groove pool via the 'groove_index' parameter. This distinguishes it from sibling tools like set_clip_groove and set_groove_amount.

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 explicit when-to-use or alternative guidance is provided. The description states what the tool does and lists parameter values, but does not mention when to prefer this over set_groove_amount or set_clip_groove. Usage context is implied but not explicit.

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