Compare lineup to listening history

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

Beyond the annotations, the description defines what 'known' means (top artists over last 4 weeks / 6 months / all time, or followed) and discloses the reorderKnownFirst side effect of reordering the draft. This adds genuine behavioral context not present in annotations, though it omits auth requirements and rate limits.

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 sentences, front-loaded with the core action, then the optional parameter effect and example use cases. Every clause carries information, though the quoted user questions add length that is slightly more illustrative than essential.

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 no output schema, the description carries the return burden and adequately conveys the result: each artist flagged as known or new, optionally reordered. It is nearly complete for a two-parameter tool, with only return-format/pagination details left unstated.

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%, so the description must carry the burden. It explains reorderKnownFirst ('puts familiar artists first') well, but draftId receives no explanation in the description or schema, relying on the surrounding context that the tool operates on a draft.

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 names a specific verb and resource: 'Mark each artist in a draft as known... or new to them.' This clarifies the ambiguous name 'compare_taste' and distinguishes it from analysis siblings like analyze_playlist or refresh_taste by emphasizing the per-artist known/new classification on a draft. It lacks an explicit tie-break against those nearest siblings, keeping it just below a 5.

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?

It supplies clear usage context with example questions ('which of these acts do I already like?', 'is this festival for me?'), which tells an agent when this tool applies. However, it never names an alternative tool or states exclusions, so routing versus refresh_taste/analyze_playlist is left to inference.

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