sonos_browse_tracks

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

No annotations exist, so the description carries full burden. It states pagination support but fails to disclose key behaviors: whether the operation is read-only, required permissions, or the format of returned data. The word 'browse' implies read-only, but this is not explicit.

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?

Extremely concise: two sentences, front-loaded with the purpose. Every word adds value, no redundancy.

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?

Missing important context: no output schema, so the description should explain return structure (e.g., track objects with properties). For a paginated tool, guidance on iteration and termination is absent. The simplicity of the tool does not fully compensate.

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?

With 100% schema coverage, the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions; it merely reiterates pagination support without detailing how count and startIndex interact.

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 it browses all tracks, distinguishing it from sibling browse tools for artists, albums, etc. The verb 'browse' and resource 'tracks' are specific and unambiguous.

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 usage for browsing all tracks but provides no explicit guidance on when to use this vs alternatives like sonos_browse_artists. It mentions pagination support but doesn't clarify when pagination is needed or how to handle large collections.

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