itunes_set_eq

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and lists example presets, omitting whether the change is global, requires playback, persists, or returns any confirmation.

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 purpose, followed by a compact Args block. There is no filler, and every sentence contributes useful information.

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 is minimally viable: it states the purpose and gives example values. However, with no annotations or output schema, it leaves gaps around error behavior, persistence, and prerequisites.

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 schema has only a string preset with default 'Off' and no description (0% coverage). The description adds meaning by naming the parameter and giving example values, but it does not provide an exhaustive list or validation 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 uses a specific verb 'Set' with a clear resource 'Apple Music Equalizer (EQ) preset', making the tool's function immediately obvious. It also distinguishes itself from sibling tools like itunes_set_volume and itunes_set_shuffle_mode.

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 intended use is implied by the action 'Set Apple Music Equalizer (EQ) preset', but there is no explicit when-to-use guidance or mention of alternatives. No exclusions are stated, but the tool is self-explanatory among the sibling set.

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