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

No annotations are provided, so the description bears the full burden of disclosing behavior such as read-only vs. mutating, pagination, rate limits, or result ordering. The description says nothing about these; it only mentions cost and payment, which is not behavioral.

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 extremely short, but this is under-specification rather than conciseness. It omits the core purpose and usage constraints, so it is not appropriately sized. The first sentence is essentially a title repeat, wasting the opportunity to add value.

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?

With no annotations, no output schema, and a vague description, the tool is severely under-documented. An agent cannot tell if it is a read operation, what parameters are required (all optional per schema), how pagination works, or what the response looks like. This is inadequate for a tool with 4 parameters and 30 siblings.

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?

The schema description coverage is 75%, so most parameters have some doc, but the tool description adds no param-specific meaning. It doesn't explain how id/username/count/cursor work together, nor clarify the cursor format. The missing 25% (cursor) is not compensated anywhere.

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 is essentially a label—'User Followers / Light Group: User'—with no explicit verb or resource statement. It doesn't say the tool retrieves a list of followers for a user; the purpose must be inferred from the tool name. It provides no differentiation from the many sibling tools that also concern 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?

There is no guidance on when to use this tool versus the numerous alternatives (e.g., get_v2_Followers, get_v1_1_FollowersIds). The only operational note is billing-related ('1 Credits', payment method), which does not help an agent decide which tool fits a task.

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