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. It discloses the preview behavior, which is a key safety trait. However, it does not mention potential side effects (e.g., irreversibility) or rate limits, but the preview mitigates risk.

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?

Two sentences, highly concise. Every word adds value. No fluff or redundancy.

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 description covers the purpose and safety preview behavior. With an output schema present, the lack of detailed return value explanation is acceptable. It could mention that unfollowing is immediate, but overall it is sufficiently complete for a simple 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%, so baseline is 3. The description does not add new information beyond what the schema already provides for the parameters. The safety note about 'confirm' is already in the schema description.

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 'Unfollow artists on Spotify', which is a specific verb and resource. This distinguishes it from the sibling tool 'follow_artists'.

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 provides a clear usage guideline: 'For safety, returns a preview unless confirm=True.' This tells the agent to first preview before actually unfollowing, which is good safety practice. However, it does not explicitly mention when to use this tool versus alternatives like follow_artists.

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