taste_shift_report

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

With no annotations provided, the description carries the full behavioral burden. It does disclose one meaningful behavioral trait — that this tool expends quota equivalent to 4× GET /me/top/* calls — which is useful for rate-limit and cost awareness. However, it does not state read-only status, output shape, or how rising/falling and Jaccard similarity are computed, leaving notable gaps.

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?

The description is a single, tightly packed sentence that front-loads the core behavior and appends the quota note second. Every word earns its place and there is no fluff. It loses a point only because the telegraphic 'rising/falling + Jaccard similarity' phrasing is slightly cramped and could mislead without elaboration.

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 the schema covering both parameters, this is a comparively complex analysis tool (four API calls, comparison logic, two windows) with no output schema and no annotations. The description omits output shape, computation semantics, read-only confirmination, and edge cases (e.g., empty windows). An agent can invoke it, but cannot predict what it returns or how to interpret the comparison, which is incomplete for a tool of this comlexity.

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 100%, so both parameters (limit and response_format) are already documented with default values, ranges, and format semantics in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 applies.

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 (Compare), a specific resource (short_term vs long_term top artists+tracks), and the concrete outputs (rising/falling + Jaccard similarity). It is clear and actionable, but it does not explicitly differentiate from conceptually overlapping siblings such as top_artist_ranking_delta, taste_checkpoint_diff, or discovery_ratio, so it stops short of 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?

No guidance is given on when to reach for this tool instead of a sibling. It never mentions alternatives, exclusions, or selection criteria, despite a crowded family of listening-analysis tools (taste_checkpoint_diff, top_track_ranking_delta, listening_report, discovery_ratio) where routing guidance would be valuable. The quota note hints at cost but not at when to use it.

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