get_v1_user_followers_by_username

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

The description provides no behavioral information beyond the basic action. With no annotations, it fails to disclose aspects like pagination (though hinted by page_id parameter), rate limits, or whether the operation is read-only. The schema suggests pagination, but the description does not explain this behavior.

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 (one sentence), but it is under-specified rather than concise. It lacks essential details that would fit in a slightly longer description. Excessive brevity reduces its utility for an AI agent.

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 the return format, pagination behavior, or how to interpret results. The presence of sibling tools also demands more context to differentiate.

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 page_id has a description). The tool description adds no additional meaning to parameters. For example, it does not explain that 'username' is the target user whose followers are fetched, or that 'count' controls page size.

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 states 'Followers By Username' and includes the HTTP path, indicating it retrieves followers for a given username. However, it does not specify the exact resource returned (e.g., list of user objects) and fails to differentiate from sibling tools like get_v1_user_followers_by_secUid or get_v1_user_following_by_username.

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 is provided on when to use this tool versus alternatives such as get_v1_user_followers_by_secUid. There is no mention of prerequisites or context in which this tool is appropriate.

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