music_search

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

Beyond readOnlyHint/destructiveHint, the description adds real behavioral context: results are bounded, an Automation permission is required for Music, and the tool returns persistent IDs rather than playing audio. These are exactly the facts that change how an agent calls it.

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?

Three short sentences, each front-loading the most decision-relevant information first (what it searches, how to filter, what it returns). No filler.

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?

An output schema exists so return values need no explanation, and the description still flags the pointer/persistent-ID shape and the permission prerequisite. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 0%, so the description carries the full burden and does: query is optional, matches name/artist/album substrings, and an empty value enumerates all results bounded. That is more than the schema's bare string type communicates.

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?

States a specific verb (search) and resource (Music library + playlists) and immediately delimits the output as 'pointers'. The clause 'no audio plays' separates it from playback siblings such as music_control, play_playlist, and now_playing without naming them.

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?

'Empty lists all, bounded' plus 'no audio plays' tells the agent both how to enumerate and when this is the wrong tool for playback. It stops short of explicitly naming music_control as the alternative, which keeps it from a 5.

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