Disconnect Spotify

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

Goes well beyond the destructiveHint/idempotentHint annotations: it enumerates exactly what is deleted (tokens.json, then config, caches, drafts, exports under purge), the two-key confirm requirement, the refusal conditions, and the fact that Spotify-side access is not revoked and must be handled by the user at an external URL.

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?

Dense but front-loaded, with the base behavior stated first and the destructive purge path second. The parentheticals (deletes tokens.json, the tool says so) are compact and earn their place, though the single long sentence requires careful parsing.

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?

Covers what is destroyed, the confirmation gate, refusal preconditions, and the out-of-band Spotify revocation step, which is what an agent needs for a destructive tool with no output schema. Nothing material is left unstated.

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 coverage is 100%, so the baseline is 3, and the description adds real meaning: purge's scope is spelled out (config, caches, drafts, exports) and confirm is constrained to a genuine in-conversation user agreement, explicitly not text embedded in posters, playlists or lineups.

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 the specific verb and resource precisely: it forgets the saved Spotify login by deleting tokens.json, and explains the extended purge variant. An agent can distinguish this from siblings like connect or setup without opening any schema.

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?

Gives explicit conditions for the destructive purge path (confirm: true, only after the user has agreed in-conversation) and states when the tool refuses (draft building, foreign files in the data folder). It does not name an alternative sibling, but the when/when-not guidance is otherwise strong.

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