list_repos

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

The readOnlyHint annotation already indicates this is a safe read operation, and the description's 'List' wording is consistent with that. However, the description adds no behavioral context beyond the scope, such as whether private repositories are included, how pagination behaves, or any rate-limit considerations.

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, front-loaded sentence with no filler or redundant phrasing. It is concise and easy to parse, though the terseness does mean some useful context is absent.

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 covers return values, and the readOnly annotation covers the safety profile, so the description is not entirely inadequate. But given the ambiguity around what kind of owner is expected and the presence of overlapping sibling tools, the description leaves meaningful gaps for an agent to resolve.

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 only rephrases the 'owner' parameter as 'owned by owner,' which adds little beyond the schema's own parameter name. The page and limit parameters are not described at all, leaving their semantics 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 uses a clear action ('List') and resource ('repositories') and identifies the scope ('owned by owner'). It is understandable, but it does not distinguish this tool from related siblings such as list_org_repos, list_my_repos, or search_repos, since 'owner' could refer to a user or organization.

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?

There is no guidance about when to use list_repos versus the many sibling list/search tools, nor any mention of alternatives or exclusion conditions. The only contextual hint is 'owned by owner,' which does not help an agent choose among list_org_repos, list_my_repos, or search_repos.

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