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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description usefully adds that only public accounts are returned and that results are paginated, but omits auth requirements and rate limits.

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?

Two sentences, front-loaded with the core action and followed by pagination behavior; no filler. The 'cursor or page' phrasing introduces a minor inaccuracy that a fully tight sentence would avoid.

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 read-only, single-required-param listing tool with an output schema already defined, the description covers purpose and pagination adequately. The dangling 'cursor' reference and lack of auth context are the only small gaps.

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 100%, so the schema already documents username, page, and per_page, setting the baseline at 3. The description adds little syntax detail and actually references a 'cursor' input that does not exist in the schema, while omitting the real per_page parameter.

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?

States a specific verb (List) and resource (public accounts followed by a GitHub user), which is clearly distinct from the inverse operation in the sibling github_user_followers. However, it never names that sibling or any other alternative, so the differentiation must be inferred.

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?

Usage is implied rather than stated: it tells the agent this returns a following list but gives no when-to-use/when-not guidance or alternatives (e.g. github_user_followers for the reverse direction). The pagination instruction ('use the cursor or page input to continue') is invocation help, not selection guidance.

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