Taste Rediscovery Recommendations

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds value by explaining the deterministic nature and clarifying this is local curation, not Spotify personalization. It does not contradict annotations.

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?

Two concise sentences with a clear front-loaded action and a clarifying note. No redundant information; 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?

With an output schema present and rich annotations, the description sufficiently covers the tool's inputs (optional limit) and behavior (sources, determinism). It lacks explicit prerequisites (e.g., whether Liked Songs sample can be empty), but this is a minor gap given the simple 1-parameter tool.

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?

The schema has 0% description coverage, and the description does not mention the 'limit' parameter at all. While the schema provides type and constraints, the description fails to explain how 'limit' applies to the output. Since coverage is low, the description should compensate but does not.

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 uses a specific verb ('Build') and clearly states the resource ('deterministic local rediscovery suggestions') and data sources (top tracks, recent plays, stratified Liked Songs sample). It also distinguishes from 'Spotify personalization', making the tool's unique scope clear among siblings.

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 provides clear context: this is for local, deterministic rediscovery rather than Spotify's personalization. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of a full usage guideline.

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