get_v2_user_followers

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions pagination via cursor and that only one page is fetched, but does not disclose authorization needs, rate limits, or the response structure. The phrase 'one request required' is vague.

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 relatively short but contains redundancy (e.g., two lines essentially repeating the same information) and awkward formatting with brackets. It could be more streamlined without loss of meaning.

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 lack of output schema and no annotations, the description is incomplete. It does not explain return values, error handling, or how to use the cursor for pagination beyond the schema. The context of sibling tools is not addressed beyond one alternative.

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 coverage is 100% with parameter descriptions already explaining user_id and page_id. The description adds minimal additional semantics (e.g., 'cursor' is mentioned but not elaborated), so it meets the baseline for high coverage.

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 it retrieves a user's followers, specifying the HTTP method, endpoint, and that it returns one page. It distinguishes from sibling get_g2_user_followers by explicitly recommending that alternative.

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 advises to prefer /g2/user/followers, offering some guidance. However, it does not explain when to use this tool over other followers-related siblings like get_gql_user_followers_chunk, nor does it clarify the meaning of 'one request required'.

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