gh_list_repos

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so safety is covered. However, the description does not disclose any additional behavioral traits such as pagination defaults, rate limits, or the effect of the 'type' parameter on the result set. The 'type: all, owner...' line is parameter semantics, not behavior.

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 extremely concise: two sentences with no fluff. It front-loads the purpose and then enumerates valid types. Every word earns its place, though it could be more informative without violating conciseness.

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?

Given the tool has 5 optional parameters and 0% schema description coverage, the description is incomplete. It does not explain the meaning of parameters like 'username' (defaults to authenticated user?), 'sort', or 'direction', nor does it clarify the semantics of 'owner' vs 'member'. The presence of an output schema covers return values, but parameter behavior remains opaque.

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 0%, so the description must compensate. It documents only the 'type' parameter values (all, owner, member, public, private, fork), but ignores 'sort', 'per_page', 'username', and 'direction'. With 5 parameters and only 1 partially explained, the description is insufficient.

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 action ('List') and resource ('repositories') with a scope ('for a user or organization'), distinguishing it from sibling tools like gh_search_repos (searching) and gh_get_repo (retrieving a single repo). This is a specific and unambiguous purpose.

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 is provided on when to use this tool versus alternatives. It does not mention that this is for browsing an owner's repos, nor does it exclude searching. The description simply states what it does without any contextual 'when-to-use' or 'use-instead' cues.

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