get_top_tracks

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

With no annotations, the description carries the full burden of disclosing behavior, but it only states a simple fact about the returned data. It does not mention that this is a read-only operation, what the result looks like, how time_range affects results, or any authentication or rate-limit expectations.

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 withno fluff or repetition. It front-loads what the tool is about. However, it offers no structure or additional detail, and its brevity edges toward under-specification rather than fully informative conciseness.

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?

Given no annotations, no output schema, and no param descriptions, this minimal statement is not complete enough to let an agent confidently select and invoke the tool in all cases. An agent would need to infer behavior, expected output shape, and the meaning of time_range from external knowledge, which is too much context to omit.

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?

The schema has 0% description coverage for its two parameters, and the description does not compensate by explaining limit or time_range. The parameter names and enum values give some hint, but the description adds no meaning beyond what is already minimally inferable from the schema.

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 that this tool returns the user's most-played tracks, which clearly identifies the resource and the kind of data provided. It is not a tautology of the tool name and is enough to distinguish it from artist- or playlist-related siblings, though it never explicitly says 'get' or 'list'.

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 about when to use this tool versus alternatives like get_top_artists, get_recently_played, or get_saved_tracks. The context is weakly implied by the phrase 'most-played,' but there is no explicit condition for choosing this tool over its siblings.

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