Spotify

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

Beyond the read-only, idempotent annotations, it discloses material operational behavior: per-resource credit costs, free failures, charge and remaining-balance reporting, cursor-based pagination, and free cached results. These details directly affect how and whether an agent should make repeated calls.

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 operational instructions and consistently formatted resource bullets make a complex dispatcher easy to scan without excessive prose. The generic, partly unsupported opening and repeated "Spotify ... 1 credit" wording introduce minor redundancy and imprecision.

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 multi-resource tool with eight parameters and no output schema, it covers the essentials needed to invoke calls correctly: resource inputs, paging, caching, costs, and failure charging. It remains short of fully complete because payload shapes are not characterized, optional search types are not explained here, and the opening lists data categories that the exposed resources do not clearly support.

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?

Although schema description coverage is 100%, the description adds useful compact signatures showing which resources accept `url|id`, which requires `query`, and which are paged. It also clarifies top-level arguments versus extras in `params`, while leaving details such as allowed search `type` values and ID or URL formats elsewhere.

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 identifies Spotify as the data source and enumerates concrete resources such as albums, artists, playlists, podcasts, search, and tracks, distinguishing it from the other platform-specific siblings. The opening reference to "profiles...collections, posts and videos" is broader than the actual resource enum, so it is not fully precise.

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?

It gives clear invocation context: choose a `resource`, supply that resource's inputs, reuse cursors for paged resources, and use `max_age_days` when a free cached copy is acceptable. It does not provide explicit when-not guidance or route the agent to alternative tools for unsupported requests.

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