list_repositories

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scoping detail ('visible to the authenticated account'), which is useful context beyond annotations. However, it doesn't disclose pagination behavior, sorting, or whether private repos are included.

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 efficient sentence that conveys the core purpose. Zero wasted words, front-loaded with the primary action.

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?

For a simple read-only listing tool with good annotations, the description is mostly adequate. However, with no output schema describing the return structure and 0% parameter coverage, some additional context about what parameters affect the listing (e.g., does 'owner' filter? what does 'account' scope?) would improve completeness. It's a simple tool, so this is acceptable but not thorough.

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 there are no per-parameter descriptions in the schema. However, the description provides no parameter semantics either—it doesn't explain what 'account', 'owner', 'limit', or 'hostname' mean in context. With 4 params and zero coverage, the description should compensate but doesn't.

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 verb ('list') and a specific resource ('repositories') scoped to the authenticated GitHub CLI account. This distinguishes it from sibling tools like get_repository (single fetch) and create_repository (creation), though it doesn't explicitly call out the 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?

No guidance on when to use this vs alternatives like get_repository or list_organizations. The description simply states what it does without explaining context (e.g., 'use this to enumerate all repos, use get_repository for a single repo'). No exclusions or alternatives mentioned.

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