get_top_tracks

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

Annotations already declare readOnlyHint=true; the description adds meaningful behavioral context by documenting the three time windows and clarifying that results are affinity-based history, not current popularity. Return-format details are covered by the output schema, so the lack of pagination prose is not a significant gap.

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 function, and each clause adds useful information. The negative clarification is compact and 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 low-complexity, read-only tool with an output schema and no required parameters, the description is nearly sufficient. It could be more complete by briefly noting pagination semantics for limit/offset, but nothing critical blocks correct invocation.

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. It does explain the important time_range parameter with concrete windows, but leaves limit and offset entirely to inference from their names. Partial compensation only.

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 a specific verb and resource: retrieve the user's most-played tracks over a time window. It also adds a distinguishing qualifier ('Spotify's own affinity ranking... not a live popularity/trending signal') that sets it apart from recent-listening or trending-style sibling tools.

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?

Implies usage for historical listening affinity rather than live trends, but does not name alternatives or give explicit when-to-use/when-not-to-use guidance. The 'not a live popularity/trending signal' clause is an implicit exclusion only.

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