spotify_query_library

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

Discloses AND logic, case-insensitive partial matching, and default limit. With no annotations, the description carries full burden but lacks details on side effects (none), authorization needs, or output structure beyond URIs.

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?

Concise, front-loaded purpose, structured Args list with no redundancies. Every line adds 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?

Covers all parameter behaviors and core purpose. Missing pagination details or mention that query is local library. Output schema exists, so return structure is partially handled. Good overall.

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%, but description provides detailed explanations for all 8 parameters, including behavior (partial match, case-insensitive, date formats). Fully compensates for schema gaps.

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 verb (query), resource (synced library), and result (matching tracks with URIs). Distinguishes from siblings like spotify_search (general search) and spotify_get_saved_tracks (saved tracks only).

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?

Implied usage for querying synced library, but no explicit guidance on when to use vs alternatives like spotify_search or spotify_library_stats. Missing when-not-to context.

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