Configure Eos OSC Fader Bank

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

Annotations already declare idempotency and non-destructiveness; the description adds valuable context beyond that, such as the 'Must be called once' prerequisite, the 're-page' behavior, and the fact that bank_index is independent of console fader numbers. No contradiction with annotations.

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 concise and front-loaded with the core purpose, followed by a clear prerequisite statement and a well-formatted Args section. No redundancy or unnecessary detail.

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?

Given the tool's simplicity (3 params, no output schema) and the existing annotations covering safety and idempotency, the description covers all essential aspects: purpose, prerequisites, parameter explanations, and repeated-use behavior. It is complete for an agent to invoke the tool correctly.

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 at 0%, the description fully compensates by documenting each parameter: bank_index (1-based, custom numbering), fader_count (how many faders), and page (optional, defaults to page 1). This adds meaningful semantics beyond the raw schema types and constraints.

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 clearly states the tool's function: 'Create (or re-page) an OSC fader bank so eos_set_fader can address it.' This specifies the verb, resource, and purpose, and distinctly connects to a sibling tool (eos_set_fader), making it unique among the listed siblings.

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 description provides clear prerequisites ('Must be called once before using a given bank_index') and explains repeated use ('Safe to call again to jump pages'). While it doesn't explicitly exclude alternatives, the context of being a required setup step for eos_set_fader gives sufficient usage direction.

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