itunes_open_location

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely says 'Open and stream' without detailing side effects (e.g., replacing current playback), error handling, or prerequisites. It does not add context beyond the bare action.

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 extremely concise, with the purpose stated in the first sentence and parameter details in the second. Every sentence serves a purpose, and it is front-loaded with the key action.

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 single-parameter tool with no output schema or annotations, the description covers the basics. However, it lacks context on when to prefer this over other playback tools and doesn't mention potential effects on current playback or return behavior, leaving some gaps.

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 adds meaningful value for the `url` parameter by specifying accepted formats: 'http://', 'https://', or 'music://'. This goes beyond the schema's bare type definition and helps the agent understand what input is expected.

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: 'Open and stream an audio stream URL or Apple Music link directly.' It specifies the action (open and stream) and the resource (audio stream URL or Apple Music link), making it distinct from siblings that play songs or control playback.

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 is given on when to use this tool versus alternatives like itunes_play or itunes_play_song. The description only implies usage when a direct URL is available, but doesn't explicitly state exclusions or compare with sibling tools.

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