taste_profile

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Get the user's top tracks,' which signals a read operation but does not explain what 'top tracks' means (e.g., time range, count, or listening context) or any other behavioral details like authorization or caching. This adds little beyond the tool name itself.

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, tightly structured sentence that front-loads the action and resource, then appends the purpose. Every word earns its place, with no redundancy or filler.

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 the tool's simplicity (zero params, output schema present), the description is reasonably complete. However, it lacks any context about whether this refers to the current user, whether 'top tracks' is based on all-time listening or recent activity, and how it relates to sibling tools. An agent might still need additional inference to use it correctly.

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 tool has zero parameters and an empty input schema, so the baseline is 4. The description correctly avoids inventing parameters and needs no parameter documentation.

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 action ('Get'), the resource ('user's top tracks'), and the intended purpose ('reason about their taste'). This distinguishes it from sibling tools focused on playback control or playlist management, and gives an agent a precise idea of what the tool returns.

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 implies its use for understanding user taste, but provides no explicit guidance on when to choose this tool over alternatives like now_playing or get_playlist_tracks. No exclusions, prerequisites, or context are given, leaving the agent to infer the appropriate usage scenario.

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