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

The read-only and non-mutating claims are consistent with the annotations but largely repeat them. The description adds useful operational context by emphasizing that only public data is returned and disclosing a cost of 1 credit per request.

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 front-loads the operation and scope, then concisely covers safety and cost. It is easy to scan, although "Read-only" and "changes nothing" are mildly redundant with each other and with the annotations.

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?

Combined with the complete input schema and safety annotations, the description is sufficient to invoke this simple paginated listing operation correctly. Its main remaining gaps are the implicit distinction from github_list_repositories and, with no output schema, the absence of any indication of what project information is returned.

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?

All three parameters are fully documented in the schema, including accepted username forms, count limits and default, and cursor-based pagination. The description adds no parameter meaning beyond that complete coverage, so the high-coverage baseline applies.

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 uses a specific verb and resource—"List a GitHub user's public projects"—and clearly states the public-data scope. It does not explicitly distinguish projects from repositories or starred items, leaving sibling differentiation incomplete.

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 wording implies use when an agent needs a particular user's public project list, but it provides no explicit selection criteria. It also does not direct agents to github_list_repositories or another sibling when a different GitHub resource is needed.

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