Unfollow an account

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

Annotations already convey idempotency and non-destructiveness. The description adds meaningful behavioral context by explaining that the tool derives the follow record from viewer state, so the caller does not need to supply a follow record ID or look one up beforehand.

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 short sentences with no filler. The core action is front-loaded, and the second sentence earns its place by clarifying a non-obvious implementation detail. Nothing is redundant.

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 mutation with a single required parameter, the description plus schema covers what the agent needs. It doesn't describe the response, but no output schema exists and unfollow outcomes are standard. Minor gap: no mention of what happens if the account isn't currently followed, though idempotentHint partially covers this.

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 the schema fully documents 'actor' and 'account'. The description's phrase 'so you only need the handle' reinforces but does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 ('Stop following an account') and goes beyond the title by revealing the mechanism (finds your own follow record from viewer state). This clearly distinguishes the tool from the sibling 'follow' and related actions.

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 intended use is immediately clear from 'Stop following an account' and the context of sibling tools. It does not explicitly contrast with mute or block, but the action is unambiguous and the note about needing only the handle provides practical guidance.

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