remove_follower

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

The description includes a 'DESTRUCTIVE' warning, indicating irreversibility, which adds behavioral context beyond the input schema. However, it does not explain what exactly is destroyed, whether notifications are sent, or any permissions needed. Given no annotations, the description partially fulfills transparency but lacks depth.

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?

The description is extremely short (one line) but lacks crucial information such as what the tool does in detail, making it under-specified rather than efficiently concise.

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?

Given the simplicity of the tool (one parameter, no annotations), the description is incomplete. It fails to explain the distinction from unfollow_user, the return value (though output schema exists), or any side effects. The required context is not provided.

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?

The input schema has 0% description coverage for the parameter user_id, and the description does not clarify its meaning or how to obtain it. The description adds no value beyond the schema field name.

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 the verb 'remove' and the resource 'a follower', and specifies the scope 'from your account'. This distinguishes it from sibling tools like unfollow_user, which is about unfollowing someone else.

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 no guidance on when to use this tool versus alternatives like unfollow_user, or any prerequisites or context for use. The usage is only implied by the purpose.

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