unfollow_user

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

No annotations are supplied, so the description carries the full behavioral burden, and it only restates the operation. It says nothing about required auth/permissions, idempotency when the account is not followed, rate limits, or whether the unfollow is reversible without re-following.

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 with no wasted words, front-loading the verb and resource. It is appropriately sized for the text it contains, though that text is thin rather than dense with useful information.

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?

This is a mutation tool with zero annotation coverage and no output schema, which raises the bar for the description. The definition does not cover preconditions, result behavior, or error cases, so an agent could call it but cannot predict the outcome.

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% for the single username parameter, so the baseline is 3. The description adds no meaning beyond the schema, such as whether @-prefixes or user IDs are accepted, but nothing is missing from the schema itself.

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?

"Unfollow a Twitter user" names a specific verb and resource, so an agent instantly knows the action. It does not explicitly distinguish itself from the sibling follow_user or state any scope limits, but the inverse relationship is clear from the name.

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 versus follow_user, no preconditions such as the target account needing to currently be followed, and no mention of effects on followers/following lists. The agent must infer everything beyond the bare action.

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