List repositories

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the project-scoping behavior ('in a project'), which is useful but not a deep behavioral disclosure; it does not mention pagination, completeness, authentication, or return format.

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 one efficient sentence with no fluff or redundancy. It front-loads the verb and resource, and every word adds meaning beyond the title.

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, one-parameter listing tool, the description plus annotations provide a minimally viable understanding. The main missing pieces are parameter format details and return value shape, which are not required for safety but would help an agent invoke it correctly without additional inference.

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 for the undocumented 'project' parameter. The description only clarifies that project is the container scope, but does not specify whether the value should be an ID, name, slug, or provide examples. This leaves a meaningful gap for correct invocation.

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 specific verb ('List'), a specific resource ('Git repositories'), and a scoping qualifier ('in a project'). This clearly distinguishes it from sibling tools like list_projects, list_branches, and list_pull_requests, so the agent knows exactly what resource is targeted.

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 description implies the tool is for listing Git repositories within a project, which gives clear context. However, it does not explicitly state when not to use it or name alternatives, so an agent must infer the appropriate selection from the resource type rather than being directly routed among the many list_* siblings.

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