get_my_top_items

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

Annotations are absent, so the description must disclose behavioral traits. It mentions no side effects, authentication needs, rate limits, or pagination behavior (though limit/offset are parameters). The description focuses on inputs, not outputs or behavior.

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 concise with a clear docstring-style parameter list. No wasted words, though the parameter descriptions could be more compact. Front-loaded purpose is clear.

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?

With no annotations, the description should cover behavioral context. It omits output description (though output schema exists), error handling, and edge cases. Adequate for a simple query tool but not complete.

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%, but the description adds meaning: explains item_type options and defaults, time_range durations, limit range, and offset default. This compensates significantly for the lack of schema param descriptions.

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 clearly states the tool retrieves the current user's top artists or tracks, a specific verb+resource combination. It distinguishes from siblings like get_my_playlists and get_recently_played.

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 on when to use this tool vs alternatives. The description only lists parameters without explaining when each option is appropriate (e.g., when to use artists vs tracks, or different time ranges). No exclusions or usage context.

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