spotify_unfollow_artists

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys only the high-level effect ('unfollow'), omitting whether the change is reversible, what authorization/scope is required, whether a response body is returned, and what happens with invalid or non-followed IDs. The maxItems=50 cap is present only in the schema, not surfaced behaviorally.

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?

A single short sentence with zero filler and the core action front-loaded. It is appropriately sized for a one-parameter tool, though it is terse to the point of omitting useful context.

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 simple one-parameter mutation with a fully documented schema and no output schema, the definition is minimally sufficient to call the tool. However, with no annotations on a write operation, additional context on reversibility or auth would materially improve completeness.

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 100% with a single well-described parameter (artist_ids, array of Spotify artist IDs), so the schema already does the semantic heavy lifting. The description adds nothing beyond what the schema provides, which matches the baseline 3 for high-coverage schemas.

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?

States a specific verb (Unfollow) and resource (artists), and the plural 'one or more' correctly signals batch operation, which distinguishes it from a hypothetical single-artist tool. It does not explicitly name spotify_follow_artists as the counterpart, but the antonym in the name is unambiguous.

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 when-to-use, when-not-to-use, prerequisites, or alternative tools are mentioned. The agent must infer everything from the tool name; no guidance on how this relates to spotify_get_followed_artists or spotify_follow_artists is provided.

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