follow_artists

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: the required OAuth scope. However, for a mutation it omits effect on existing data, idempotency on duplicate follows, and failure behavior, so it is only partially transparent.

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?

One short sentence, front-loaded with the action and immediately followed by the auth constraint. No filler, though it is arguably terse to the point of under-specification for a write operation.

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?

The tool is simple (one array param, no output schema) so the minimal description is close to sufficient, and the auth scope is covered. But ambiguity remains about whether 'items' truly accepts artist names/URIs given the schema text says 'Track names', and nothing describes the result of the operation.

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% and there is a single required parameter, so the schema already documents 'items' fully. The description adds nothing about batching or limits. Note a schema mismatch worth flagging: the items field says 'Track names OR URIs' while the tool follows artists.

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 (follow) and resource (artists), which an agent can distinguish from unfollow_artists and followed_artists by verb alone. It stops short of explicitly contrasting with those siblings, so it is clear but not sibling-differentiating.

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 only guidance is the parenthetical 'needs follow scope', which is a prerequisite rather than a when-to-use condition. It never says when to prefer this over followed_artists (checking) or unfollow_artists (reversing), nor what happens on repeat calls.

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