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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without the prose. The description adds two genuinely new facts — ordering is 'newest push first' and the result set is limited to repos the app can reach — but says nothing about pagination or truncation 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?

A single tight sentence with the resource and scope front-loaded and zero filler. Slightly awkward as a bare noun phrase rather than a verb-led statement, but nothing is wasted.

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 three-parameter read-only list with rich annotations and no output schema, the description covers scope, ordering, returned fields and filters. The only meaningful gap is the undefined semantics of the 'owner' and 'search' filters.

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 only 33%: 'limit' is documented in the schema, but 'owner' and 'search' have no schema descriptions at all. The description names both as filters but gives no format for owner (login vs org) and no indication of what fields 'search' matches, so it does not compensate for the coverage gap.

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 identifies the specific resource (repositories reachable by the AskYourStack app) and adds distinguishing scope plus the fields returned (visibility, default branch, language). It is clear what the tool does, but it never explicitly contrasts itself with the nearby single-repo tool (gh_repo) or gh_create_repo, so sibling differentiation is left implicit.

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?

'Filter with owner or search' implies how to narrow results, which is a light form of usage guidance. There is no statement of when to pick this over gh_repo/gh_repos alternatives, nor any note on exclusions or prerequisites beyond the implicit read-only nature.

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