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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral fact beyond that: results are limited to 'public' repositories, meaning private/auth-scoped repos are excluded. It says nothing about pagination, ordering, or result caps, which the schema hints at but does not explain.

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?

A single front-loaded sentence with the resource and scope stated immediately and zero filler. Nothing could be trimmed without losing meaning.

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?

An output schema exists, so return values need not be described, and the annotations cover the read-only/open-world profile. However, for a six-parameter paginated list endpoint the description is silent on pagination behavior and result limits, leaving the agent to infer them from the schema alone.

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 all six parameters (page, sort, type, per_page, username, direction) are already documented in the schema. The description only restates the username/ownership relationship and adds nothing about sort defaults, valid combinations, or pagination semantics, so the baseline 3 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?

States a specific verb and resource ('Returns the public repositories owned by a GitHub user'), so an agent knows exactly what it fetches. It does not name or distinguish itself from close siblings like github_org_repos, github_user_pinned, or github_search_repositories, which leaves differentiation to inference.

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 phrase 'owned by a GitHub user' hints at the input shape but gives no explicit when-to-use guidance. With siblings such as github_org_repos, github_search_repositories, and github_user_pinned in the same namespace, the agent gets no routing rule for choosing this tool over them.

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