get_top_tracks

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

Annotations are absent, so the description must carry the full burden of behavioral disclosure. It only says 'Get', implying a read operation, but does not explicitly state it is non-destructive, does not mention authentication requirements, rate limits, or any side effects. There is no mention of pagination behavior or how results are ordered. For a simple getter this may be adequate, but given no annotations, more disclosure would be expected.

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, concise sentence with zero wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. There is no unnecessary 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?

For a simple getter with no output schema and well-documented parameters, the description is adequate but not complete. It does not mention any prerequisites (e.g., user authorization), nor does it hint at the response format. However, given the low complexity and clear schema, an agent could call it without missing critical information.

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% for both parameters ('limit' and 'time_range'), with complete descriptions of ranges and defaults. The tool description adds no additional meaning beyond what the schema already provides, so the baseline of 3 applies as the schema does the heavy lifting.

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 'Get the user's most-played tracks' uses a specific verb ('Get') and a precise resource ('user's most-played tracks'). It clearly distinguishes this tool from siblings like get_top_artists (artists vs tracks) and get_recently_played (recent vs top). The purpose is unambiguous and easily matches an agent's intent.

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 no guidance on when to use this tool versus alternatives. It does not mention that get_top_artists should be used for artists, or that get_recently_played is for recent history. An agent must infer usage from the name and purpose, which is not explicitly stated.

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