Get X User Following

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

Annotations already declare the operation safe (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds return-value details ('usernames, bios, and follower counts') but provides no additional behavioral context like pagination, rate limits, or edge cases.

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 a single concise sentence, front-loaded with the verb and resource. Every word contributes to understanding, with no repetition or fluff.

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 read-only list tool with clear schema and annotations, the description is adequate: it states the operation and return content. It does not explicitly disambiguate from x_get_followers, but the wording 'account follows' is unambiguous enough for most agents.

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%, with all three parameters (username, limit, response_format) already described. The description adds no further parameter semantics beyond mentioning a 'specified account,' which maps naturally to the username parameter.

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 ('Get') and resource ('list of users that a specified account follows'), clearly distinguishing it from the sibling tool x_get_followers which would be users following the account. It also notes the returned fields (usernames, bios, follower counts).

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 clearly states what the tool does ('users that a specified account follows'), giving the context for when to use it. However, it does not explicitly name alternatives or exclusions, such as 'use x_get_followers for users following the account.'

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