get_users_by_id_followers

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

Annotations already communicate readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds some context by clarifying that id can be the slug or 'me' for the authenticated user, which implies authentication requirements. It does not cover pagination, rate limits, or response caveats.

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 concise and well-structured: a one-line summary, the endpoint, and a terse args block. There is no wasted text, and the most important information is front-loaded.

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 follower fetch with an output schema and rich annotations, the description is largely sufficient. It covers both parameters and the meaningful 'me' special case. Minor gaps such as pagination behavior and the exact shape of extended information are not critical given the output schema.

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%, so the description is the main source of parameter meaning. It usefully explains that id is a slug and supports 'me' for the authenticated user. The 'extended' parameter explanation is vague, only saying it includes extended information, without detailing what values or formats are expected.

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 a specific verb and resource: 'Get followers' plus the exact GET endpoint. This is clearly distinct from sibling tools like get_users_by_id_following, since it targets followers rather than followed users.

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 imperative 'Get followers' implies the intended use case, but there is no explicit guidance about when to choose this over related sibling tools such as get_users_by_id_following or get_users_by_id_friends. No alternatives or exclusions are mentioned.

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