get_top_rated_tracks

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, but the description adds no further behavioral context such as sorting order, tie-breaking, whether unrated tracks are excluded, or any permission requirements. It essentially restates the tool name without disclosing observable behavior beyond the obvious.

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 extremely concise: a one-sentence purpose, followed by a simple Args/Returns structure. Every line earns its place and the front-loaded purpose sentence makes the tool's function immediately obvious.

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 one-parameter tool with an output schema, the description covers the basic purpose, parameter, and return type. However, it lacks any mention of sorting behavior, default behavior when limit is omitted, or guidance on when to choose this over sibling tools. It is minimally viable but has clear gaps.

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 input schema only provides the type and default for 'limit'. The description explicitly defines limit as 'Maximum number of tracks to return', which adds meaning beyond the schema. This compensates for the 0% schema description coverage.

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 starts with the specific verb 'Get' and resource 'highest rated tracks in the library', clearly distinguishing it from sibling tools like get_most_played_tracks (play count) or get_tracks_by_key (key). It is immediately clear what the tool does and how it differs.

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 context is clear: use this when you need top tracks sorted by rating. However, there is no explicit when-not or alternative naming to distinguish it from similar listing tools, so usage is implied rather than explicitly stated.

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