get_user_followers

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get followers list' with no details on pagination, privacy restrictions, authentication, or output shape. This is a significant gap even for a read operation, as the agent cannot anticipate behaviors like default user_id handling or limit semantics beyond the schema.

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 a single concise sentence with no redundant words. It efficiently communicates the core purpose without unnecessary elaboration, fitting the simplicity of the tool.

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?

For a simple read-only tool with full schema coverage, the description is minimally adequate. However, it lacks any mention of return value details, pagination behavior, or edge cases like private accounts. Given the absence of an output schema and annotations, the description should do more to explain what the agent can expect from the call.

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 input schema already has 100% description coverage for both parameters (limit and user_id), so the baseline is 3. The tool description itself adds no parameter-specific information, neither supplementing nor clarifying what is already structured.

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 the action (Get) and the resource (followers list) for a user. It distinguishes from sibling tools like get_user_following by specifying 'followers' rather than 'following', and from analytics tools by focusing on the list itself.

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?

The description provides no explicit guidance on when to use this tool versus alternatives such as get_user_following or get_follower_growth_analytics. There is no mention of exclusions, prerequisites, or common scenarios, leaving the agent to infer usage solely from the name.

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