Unfollow a user

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

Discloses that this acts on a real account and is rate-limited, which goes beyond the annotations (idempotentHint=true, destructiveHint=false) by highlighting risks and constraints.

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, immediately front-loaded with purpose. Warning and context efficiently added with no wasted words.

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 simplicity (1 param, no output schema), the description adequately covers purpose and risks. Could mention success/error behavior, but idempotentHint reduces need. Slightly incomplete but sufficient for this tool.

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 covers 100% of parameters with description, so baseline 3. The description adds 'by @handle' but this is already implied; no additional semantics beyond schema.

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 'Unfollow' and the resource 'Threads user by @handle', distinguishing it from sibling 'follow_user' and other tools.

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?

Provides explicit warning against burst usage and mentions rate-limiting, guiding agents to avoid ban triggers. Does not explicitly name alternatives but context implies careful scheduling.

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