github_users_list_followers_for_user

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

No annotations are provided, so the description carries full burden. It fails to disclose pagination behavior (despite parameters hinting at it), rate limits, or ordering of results. The description is too sparse to inform the agent about 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 a single concise sentence that is front-loaded. It contains no superfluous words, making it efficient. However, it could be slightly improved without losing conciseness.

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 list-followers tool, the description is minimally adequate but lacks details like response format (list of user objects), pagination hints, and scope (requires username). Given no output schema and no annotations, more context would help.

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?

Input schema has 100% coverage with descriptions for each parameter, so baseline is 3. The description does not add extra meaning beyond the schema; 'username' description is merely a repetition. The pagination parameters are well-described in the schema, so no deduction.

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 'List followers of a user' clearly specifies the action (list) and the resource (followers of a user). It effectively distinguishes from siblings like 'list_followers_for_authenticated_user' and 'list_following_for_user' by specifying 'of a user'.

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 guidance on when to use this tool versus alternatives like github_users_list_followers_for_authenticated_user. It does not mention prerequisites or filtering context, leaving the agent to infer usage from the name alone.

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