get_v1_user_followers_chunk

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

Description mentions pagination with a cursor but doesn't explain how cursors work, what the 'one request required' means, or any behavioral details like rate limits, authentication, or error handling. Lacks transparency given no annotations.

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 with a parenthetical; no wasted words but slightly unstructured. Could be more informative without major length increase.

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?

Despite low complexity (2 params, no output schema), the description lacks essential details about the pagination mechanism, response structure, and how to iterate through pages. Incomplete for practical use.

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 does not clarify parameters beyond their names. The term 'cursor' is mentioned but not linked to max_id parameter. No additional meaning provided.

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 that the tool retrieves a paginated chunk of followers using a cursor. It distinguishes itself from sibling tools by noting 'one request required', but lacks explicit differentiation from similar chunk 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?

No guidance on when to use this tool versus alternatives like get_v2_user_followers or get_gql_user_followers_chunk. No conditions for use or when not to use.

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