Retrieve a page of public GitHub accounts a specified username follows, with pagination controls for scanning their following list.
List who a GitHub user follows. Returns a page of the public accounts a GitHub user follows.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number | |
| per_page | No | Results per page (max 100) | |
| username | Yes | GitHub username |
Changes observed during successful MCP inspections.
v1.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions that it returns 'a page of the public accounts', disclosing pagination and public-only scope. However, with no annotations provided, it lacks details on authentication needs, rate limits, or behavior for invalid usernames.
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 with two clear sentences. Every word is necessary and front-loaded effectively.
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 listing tool with no output schema, the description is adequate but vague about the returned fields. It mentions 'public accounts' but does not specify what data is included for each account.
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 coverage is 100%, so parameters are already documented. The description adds no additional meaning beyond the schema definitions.
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 'List who a GitHub user follows' with a specific verb and resource. However, it does not explicitly distinguish from the sibling tool 'github_user_followers', relying on the name alone for differentiation.
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 on when to use this tool versus alternatives, such as when to use 'github_user_followers' instead. No exclusions or context are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.