github_user_repos

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal two meaningful traits: only public repositories are returned, and the result is paginated. However, it does not mention authentication needs, rate limits, error behavior for nonexistent users, or whether sorting/pagination defaults apply.

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 two sentences with no filler, front-loads the core action, and the parenthetical tech-stack signal adds useful intent without bloat. The slight repetition of 'public repositories' is acceptable because the second sentence contributes pagination and purpose.

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?

The tool is simple and the schema covers all parameters, so the description need not re-document them. Still, with no output schema and no mention of return fields or how to navigate pages, plus no differentiation from several GitHub sibling tools, the description leaves moderate gaps for an agent deciding whether this is the right call.

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 all six parameters including enums and max per_page. The description adds no parameter-level meaning beyond restating that a page is returned, which is baseline behavior for a list endpoint.

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 the verb ('List') and resource ('a GitHub user's public repositories'), and adds the context that this is a tech-stack signal. However, it does not explicitly distinguish this tool from closely related siblings like github_org_repos or github_user_pinned, so it stops short of full sibling 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?

There is no explicit guidance on when to use this tool versus alternatives. The 'tech-stack signal' hint implies a use case, but the description never states when to choose this over github_user_pinned, github_org_repos, or github_search_repositories, and it gives no exclusions or prerequisites.

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