Get Spotify Track Audio Features

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

While annotations already indicate read-only, idempotent, and non-destructive behavior, the description adds substantial detail: it explicitly returns missing tracks/fields, field-level provenance, retained conflicts, and user overrides, and specifies the auto-mode fallback condition. This goes well beyond the annotation baseline.

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 three sentences, each serving a clear purpose: main action, return contents, and source behavior. It is front-loaded with the primary verb and resource, with no redundant or filler text.

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 a rich output schema and comprehensive annotations, the description covers all essential aspects: what the tool does, key input semantics, expected output details, and provider fallback logic. It is sufficiently complete for an agent to select and invoke the tool 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?

Given 0% schema description coverage, the description compensates by clarifying that track_ids are exact Spotify IDs, explaining the 'auto' source fallback behavior, and mentioning user overrides. It does not detail each override field, but the schema provides constraints and descriptions for those nested properties.

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 gets typed audio measurements for specific Spotify track IDs, using a specific verb and resource. It distinguishes itself from sibling tools like spotify_audio_compare and spotify_audio_audit by focusing on raw measurements and detailed return metadata (missing tracks, provenance, conflicts, overrides).

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 use for retrieving audio features but does not explicitly state when to choose this tool over alternatives or provide exclusions. It gives context on the 'source' parameter fallback behavior, but no direct guidance on tool selection versus sibling tools.

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