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

No annotations are provided, so the description must disclose behavior. It does not mention whether this is a read-only operation, any authentication requirements, rate limits, or what happens on error. The 'Billing per call' hint is the only behavioral note, but it doesn't describe the tool's actual behavior or side effects.

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 that's underspecification rather than conciseness. It is not structured to help an agent; it's just a phrase plus billing metadata. Every word is essentially wasted because it adds no actionable information.

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 annotations, output schema, and parameter descriptions, the tool is completely under-specified. An agent cannot know what data is returned, how to construct a valid request, or what edge cases exist. The complexity of 4 parameters with no guidance makes this far from complete.

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%; the description does not explain any of the four parameters (cursor, userId, proxyUrl, resFormat). Agents receive no hints about what each parameter controls, requiredness, or format. This is a critical gap given no parameter descriptions.

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 essentially restates the name and title: 'get blueVerifiedFollowers by V2'. It adds only 'Group: follows' and billing info, which do not clarify what the tool does or what 'blueVerifiedFollowers' means. It fails to distinguish from sibling follow-related tools like followersListV2 or followsIds.

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. With many siblings (followersList, followersIds, followingsList, etc.), the description offers no context for selection. It does not mention any prerequisites or scenarios.

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