mixer_get_eq

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

No annotations provided, yet the description omits behavioral traits such as whether the operation is read-only, what happens if the track parameter is invalid, or if it returns live data. It only states the return content.

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?

Single sentence with no waste. Front-loads the action and return content.

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 no output schema, the description hints at return values (gains + frequencies) but lacks structure or details. For a simple one-parameter tool, it is somewhat adequate but incomplete.

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 sole parameter 'track' is not described in the description; there is no explanation of its meaning (e.g., zero-based vs one-based indexing, valid range, or requirement). 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 clearly states it returns a 3-band mixer EQ with gains and frequencies, using a specific verb (Return) and resource (mixer EQ). It distinguishes from sibling tools like mixer_set_eq_band (which sets a band) and mixer_track_info (general track info).

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 guidance on when to use this tool versus alternatives like mixer_set_eq_band. No mention of prerequisites (e.g., track existence) or exclusions.

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