top_tracks

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no indication that it is a read-only personalization call, no defaults for limit or time_range, no pagination or result-shape context. It adds only the existence of three time windows, which the schema enum already implies.

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?

A single short sentence with no wasted words and the resource front-loaded, but brevity here reflects under-specification rather than efficient communication; nothing about defaults or usage is stated.

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 simple two-parameter read tool with no output schema, the description should at minimum state defaults (limit, time_range) and that it returns ranked tracks for the authenticated user. None of that is present, leaving the agent guessing at call semantics.

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 compensate for both parameters. It gestures at the time_range enum values ('short/medium/long term') but adds no default, format, or meaning, and completely omits the limit parameter. Half the parameter surface is undocumented.

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?

States the resource ('your top tracks') and scope ('short/medium/long term'), which implicitly distinguishes it from siblings like saved_tracks (library) and recent_tracks (history). However, no explicit verb and no direct sibling comparison, so an agent must infer that this returns ranked listening stats rather than a saved collection.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., user auth), and no routing to alternatives such as recent_tracks for history or recommendations for discovery. The agent is left to infer usage purely from the name.

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