itunes_reveal_track

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

The description discloses the core behavior (reveal and highlight) and the special case of an empty parameter. No side effects are mentioned, but for a simple UI action this is acceptable.

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 brief and to the point, with no unnecessary information or repetition. Two sentences cover the essential aspects.

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 tool with a single optional parameter and no output schema, the description covers the purpose, parameter behavior, and special case. It lacks explicit mention of side effects or return values, but these are not critical for such a simple action.

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 explicitly explains the 'song' parameter: it is an optional track title, and if empty, reveals the currently playing track. This adds meaningful context beyond the schema's default value.

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 action (reveal and highlight) and the resource (track in the main Music app window). It distinguishes from sibling tools like play, pause, or search.

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 implies when to use it (to reveal a track in the UI) but does not explicitly contrast with alternatives or provide context on when to prefer this over other actions.

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