Set FX parameter

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Set' but does not mention persistence, side effects, undo behavior, error conditions, or that this modifies track/FX state. This is a meaningful gap for a mutating tool.

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?

Two tight sentences, no filler, and the primary action is stated immediately. The reference to the discovery tool is placed directly after the action, keeping the description efficient and easy to parse.

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?

The description is adequate for a simple setter but not fully complete: it names the discovery approach and the value constraint, yet omits how to obtain track/fx indices and does not describe return behavior or side effects. Given four required parameters and no output schema, this leaves some gaps for an agent to infer.

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 only 25%, so the description must compensate, but it only partially does. It explains that parameter indices and ranges come from reaper_get_fx_params, yet it leaves track_index and fx_index semantics undocumented and provides no concrete guidance about units or zero-based indexing.

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 states a specific verb and resource: 'Set one parameter of an FX by parameter index.' It also distinguishes the tool from the discovery sibling by pointing to reaper_get_fx_params, so an agent can tell this is the mutating counterpart.

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 instruction 'Use reaper_get_fx_params to discover indices and ranges' provides clear context and a prerequisite for using this tool correctly. It does not explicitly enumerate when not to use it versus other sibling tools, but the discovery guidance covers the main ambiguity.

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