unlink_account

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description's contribution is identifying what is destroyed (the saved username), but it says nothing about whether other account data, progress, or history survives, nor about error behavior for unlinked platforms.

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 front-loaded sentence with no filler, which is efficient. However, for a destructive operation the terseness shades into under-specification rather than optimal sizing.

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?

An output schema exists so return values needn't be described, and annotations cover the safety traits. Still, a destructive one-parameter tool with 0% schema coverage should state prerequisites, the scope of deletion, and failure behavior, none of which appear.

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?

Only one parameter exists and schema coverage is 0%, so the description must carry the meaning. 'For a platform' maps the parameter to its role, but it gives no format, casing, or validity guidance (e.g. whether it must be one of list_platforms' values), so the compensation is partial.

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 uses a specific verb and resource ('Forget the username saved for a platform'), which is clearly distinct from the sibling link_account. It falls short of 5 only because it doesn't explicitly name the counterpart operation or clarify whether anything beyond the username is affected.

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?

There is no guidance on when to use this instead of alternatives, no mention of prerequisites such as the platform needing to be linked first, and no statement about what happens if the username was never saved. The agent must infer all of this.

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