Top Artists and Tracks

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: the valid time-range meanings, limit bounds, and that the return object will populate only one of 'tracks' or 'artists' based on item_type.

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 front-loaded with the core action and uses a compact Args/Returns structure. The context paragraph about withdrawn endpoints adds strategic value for selecting the tool, though it is not strictly required for invoking it. Overall, each section earns its place without padding.

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?

All three parameters are documented, the return shape is named, and annotations plus an output schema cover the remaining operational details. Minor gaps remain, such as not spelling out the time_range default in the description, but the schema fills that in. The tool can be called correctly from the description and existing structured data.

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 fully carries the parameter documentation. It explains every parameter in plain language: item_type values with default, time_range definitions with approximate durations, and limit range (1-50) with default. This goes well beyond the bare 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 a specific verb and resource: 'Get the user's top artists or tracks over a time range.' It also clarifies the core toggle between item types. It does not explicitly differentiate itself from siblings such as get_recently_played or get_me, so it stops short of a 5.

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 gives clear context for when this tool matters: with recommendations, audio-features, and related-artists withdrawn, this is 'the measured foundation for taste profiling and building suggestions.' It does not list exclusions or alternative sibling tools, but the intended use case is clear.

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