get_gql_user_followers_chunk

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

No annotations provided, so the description carries full burden. It mentions billing (2 requests per call) but does not disclose behavior regarding pagination, rate limits, or account privacy checks (though 'force' parameter hints at it). The return format is not described.

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 very brief (one sentence), but it includes useful billing info and the API path. However, it lacks necessary details to be fully self-contained. It's not overly verbose, but conciseness here comes at the expense of completeness.

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 tool has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain how to use pagination (end_cursor), the effect of 'force', or what the response contains. The complexity of a chunked follower fetcher is not addressed.

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 only 33% (only 'force' has a description). The tool description adds no parameter information beyond the schema. 'user_id' and 'end_cursor' are not explained, relying on the schema which is insufficient.

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 and includes the API path. However, the phrasing 'Get a user followers' is slightly grammatically awkward and doesn't explicitly mention the required 'user_id' parameter. It distinguishes from siblings like 'get_gql_user_following_chunk' via the noun 'followers'.

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 sibling tools like 'get_v1_user_followers_chunk' or 'get_gql_user_following_chunk'. The phrase 'one request required' is ambiguous and does not explain pagination or batch usage.

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