get_g2_user_followers

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

No annotations are provided, so the description carries full burden. It mentions pagination with a cursor but does not disclose edge cases, error handling, rate limits, or whether it is a read-only operation. The phrase 'one request required' is ambiguous.

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 sentences are efficiently written with no fluff. The first sentence states the endpoint and purpose, the second adds pagination detail. Could be slightly more concise but acceptable.

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?

The tool is a paginated list operation with no output schema. The description lacks details on pagination mechanics, return format, or how it differs from sibling follower tools. More context is needed for effective usage.

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 0%, and the description only hints that page_id is a cursor. user_id is self-explanatory from the name, but the description adds minimal meaning beyond the schema. For 0% coverage, it should provide clearer parameter explanations.

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 gets a user's followers, one page per request with cursor. The verb 'get' and resource 'user followers' are specific. However, it does not differentiate from sibling tools like get_v1_user_followers_chunk or get_v2_user_followers, which have similar purposes.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, pagination strategy, or why to choose this over many similar follower endpoint tools in the same server.

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