spotify_discover_deep_cuts

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

No annotations provided, so description carries full burden. It only states the function without disclosing authentication requirements, rate limits, edge cases (e.g., no deep cuts), or return format. Description is insufficient for a tool with zero annotation coverage.

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 sentence with no redundancy. Directly states purpose and definition of deep cuts. Every word earns its place.

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?

Despite having only 2 parameters and an output schema, the description is too minimal. It assumes knowledge of Spotify IDs and what 'deep cuts' means operationally. Does not mention return structure or differentiation from many sibling tools.

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 description coverage is 0%. Description does not explain what 'artist_id' represents (e.g., Spotify ID) or what 'limit' controls (e.g., number of tracks). No additional meaning added beyond the schema's basic types and defaults.

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 verb 'Find', resource 'deep cuts', and defines deep cuts as 'album tracks that were not released as singles'. This distinguishes it from similar sibling tools like 'spotify_artist_deep_dive' or 'spotify_discover_by_artist'.

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 is clear for finding deep cuts, but there is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or when not to use it.

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