spotify_get_audio_features

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

No annotations are provided, so the description must carry the full burden. It only states 'Get', implying a read operation, but does not disclose authentication requirements (bearer_token is required), rate limits, or any side effects. The description fails to add behavioral context beyond the basic action.

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 14-word sentence, concise and front-loaded with the core purpose. However, it sacrifices key details like parameters and authentication, which prevents a higher score.

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 no output schema and no annotations, the description is incomplete. It does not explain how to obtain a track_id, mention authentication, handle errors, or describe the output format. Important context for a tool with two required parameters is missing.

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%, and the description does not mention either of the two required parameters (bearer_token, track_id). It does not add any meaning beyond the schema, leaving the agent to infer usage from parameter names alone.

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 verb 'Get' and the resource 'audio analysis features (danceability, energy, tempo, etc.) for a Spotify track'. It specifies the kind of data and provides examples, distinguishing it from sibling tools like spotify_get_track which returns metadata.

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 offers no guidance on when to use this tool versus alternatives, such as when to prefer this over spotify_get_track or spotify_get_recommendations. No exclusions or context for usage is provided.

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