sonos_get_favorite_radio_stations

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

Description accurately describes a read operation returning metadata and URIs. No annotations are present, so no contradiction. Adds context beyond schema by specifying 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, front-loaded sentence with no redundancy. Every word provides value.

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 retrieval tool, the description explains the return value. Lacks error conditions or prerequisites, but is sufficient given no output schema and well-schematized parameters.

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?

Parameter descriptions in schema cover 100% of parameters with defaults and purpose. Description does not add extra meaning beyond 'Get favorite radio stations'.

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?

Clearly states 'Get favorite radio stations from Sonos favorites' with specific verb and resource. It distinguishes from sibling browse/search tools by focusing on favorites.

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 explicit guidance on when to use this tool versus alternatives like sonos_browse_music_service or sonos_search_library. The description implies it's for favorite stations but lacks when-not-to-use info.

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