top_items

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

Annotations already cover read-only, idempotent, and open-world behavior, lowering the burden on the description. The description adds a useful note about the server-side local default for username, but it does not disclose other behaviors such as result ordering, pagination, or rate limits.

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 two concise sentences with no filler. The core function is front-loaded, and the username note is a necessary operational detail.

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 4-parameter tool with no output schema, the description covers the essential inputs and one configuration nuance, but it omits any hint of return format, how 'top' is defined, or the meaning of the limit parameter. This leaves some gaps for an agent.

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 50%, so the description must compensate. It adds meaning for kind (artists/albums/tracks), period (selectable period), and username (pass unless local default), but it does not mention limit at all. This is partial compensation at best.

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 ('Get') and resource ('top artists, albums, or tracks for a Last.fm user') with a period selector, which clearly conveys the tool's function. It does not explicitly contrast with siblings like recent_scrobbles or artist_history, so it misses the top distinction.

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?

There is no guidance on when to use this tool instead of recent_scrobbles, artist_history, or rediscovery_candidates. The only usage note is about the username default, which is a parameter detail, not a selection criterion.

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