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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions billing and group, but does not disclose whether authentication is required, whether pagination via 'cursor' is supported, whether results are limited, or what side effects (if any) occur. The verb 'get' implies a read operation, but this is implicit and underdeveloped.

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 short, but this is under-specification rather than effective conciseness. The main sentence is redundant with the tool name and title, and the billing/group metadata, while useful, does not make up for the absence of substantive content.

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?

There is no output schema, no annotations, and no meaningful description of return values, pagination, or parameter behavior. The tool's purpose is only vaguely implied, and the description is nowhere near sufficient for an agent to understand what this tool returns or how to use it correctly, especially given the large set of similar sibling tools.

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 0% and the description adds no parameter information whatsoever. The parameters 'cursor', 'userId', 'proxyUrl', and 'resFormat' remain unexplained, especially 'proxyUrl' and 'resFormat', which are non-obvious. The description does nothing to compensate for the lack of schema-level documentation.

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 'get followersList by V2' essentially restates the tool name and title, providing no explanation of what a 'followersList' is or what data it returns. It does add 'Group: follows' but this is categorization, not a clear functional definition. It also does not distinguish itself meaningfully from sibling tools like 'followersList' or 'blueVerifiedFollowersV2' beyond the V2 label.

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?

There is no guidance on when to use this tool versus alternatives. The description only restates the action and mentions billing; it does not explain the intended use case, prerequisites, or scenarios where another tool (e.g., 'followersIds') would be more appropriate.

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