list_user_repos

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

With no annotations provided, the description must disclose behavioral characteristics on its own, but it only says `List`. It does not mention pagination, sort defaults, whether private repositories are returned, authentication needs, or any other runtime behavior an agent should know.

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 with no filler words. The action and object are front-loaded, making it highly scannable and easy to process.

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 output schema likely covers return shape, so lack of return documentation is acceptable. However, the description is still thin for a tool with no annotations and incomplete parameter semantics; pagination and sorting behavior are not addressed and need to be divined from the schema defaults.

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?

Given the schema has 0% parameter description coverage, the description should compensate by explaining at least the main parameters. It clarifies that `username` identifies the GitHub user, but it gives no meaning or allowed use for `sort` and `per_page`, leaving half of the parameters to inference.

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 states a specific action (`List`), a resource (`repositories`), and a clear scope (`for a GitHub user`), making the endpoint immediately distinguishable from siblings like search_repositories or get_repository. Its meaning is unambiguous and can be understood without opening the schema.

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 does not say when to prefer this tool over alternatives or when not to use it. There is no mention of search_repositories for broad search or get_repository for a single repo, so the agent receives no explicit usage guidance.

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