top_track_ranking_delta

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

With no annotations provided, the description carries the burden, and it does well by disclosing the quota cost (2× GET /me/top/tracks), the sort behavior (climbers first), and the default windows. It does not over-explain side effects, but 'Show' pluas a read-only report.

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 senences deliver purpose, ordering, default window pairing, and quota information with no redundancy. The key behavior is front-loaded and every clause 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?

For a read-only report tool with four optional enum/limited parameters and no nested objects, the description plus schema covers selection and invocation well. It does not detail edge cases like unranked tracks or the exact JSON output shape, but the purpose and response_format defaults are sufficient for a typical call.

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?

Input schema coverage is 100%, and all for parameters already have descriptions and defaults. The description reinforces the short_term/medium_term defaults but adds no genuinely new parameter semantics beyond the schema. Baseline 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 states a specific operation: show how each top track's rank moved between two time windows, with climbers first and a concrete default pairing. This clearly distinguishes it from static ranking siblings like top_track_leaderboard and from the artist-focused top_artist_ranking_delta.

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 implies the tool is for rank-movement comparisons and states the default windows, but it does not explicitly say when to prefer this over siblings such as top_track_leaderboard or top_artist_ranking_delta. There is usable context, yet no explicit alternatives or exclusions.

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