get_user_followers

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

With no annotations, the description must carry the behavioral disclosure burden, but it fails to mention the return format (full user objects vs IDs), pagination via cursor, authentication requirements, or any rate limits. The truncated rest_id instruction does not disclose behavioral traits.

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 brief but ends with an unfinished sentence ('from "'), which is a structural failure. This is not concise communication but rather an incomplete thought that harms comprehension.

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 tool with no output schema and no annotations, the description should at least explain what the tool returns and how pagination works. It also needs to clarify how it differs from get_user_followers_ids, but instead leaves significant gaps due to truncation.

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 descriptions are only example values (100% coverage), so baseline is 3. The description adds a marginally useful hint about 'user(rest_id)' but is incomplete, and count/cursor semantics remain unexplained except by examples.

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 'Get User Followers By ID', which clearly identifies the action and resource. However, it does not distinguish this from sibling tools like get_user_followers_ids or get_user_verified_followers, and the truncated sentence about rest_id adds ambiguity rather than clarity.

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. The partial sentence 'You can get the user(rest_id) query from' seems to be a prerequisite hint but is cut off and does not address tool selection.

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