sonos_browse_music_service

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

Discloses critical behavioral trait: returns empty results/errors if not authenticated. Notes only 'Anonymous' services work without auth. With no annotations, description carries full burden and covers the most important behavioral aspect. Could detail return format or pagination but suffices.

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?

Two sentences plus a warning. Every sentence is purposeful: states action, warns about authentication, provides alternative tool. No redundancy or fluff. Front-loaded with the main purpose.

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 5 parameters, no output schema, and many sibling tools, description covers the essential context: authentication dependency, alternative for radio stations, and nesting via containerId. Lacks explicit mention of pagination or return structure but schema handles param details.

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?

Schema covers all 5 parameters with descriptions. Description adds value by explaining containerId usage (root or previous browse ID) and serviceName examples. Baseline 3 due to 100% schema coverage; description provides modest additional context.

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?

Description clearly states the tool browses content from a music service. It distinguishes from sibling tools like sonos_browse_artists and sonos_get_favorite_radio_stations by specifying the generic browsing functionality and warning about authentication.

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?

Explicitly warns that most services need authentication and will fail otherwise. Suggests checking authType via sonos_list_music_services and recommends sonos_get_favorite_radio_stations for pre-configured stations. Provides clear when-to-use and when-not-to-use guidance.

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