list_repositories

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

With no annotations, the description carries the full burden of behavioral disclosure. It does establish read-only behavior ('List repositories visible...') and documents the response shape, but it does not mention authentication requirements, rate limits, or edge semantics such as the exact meaning of has_more or raw=true.

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 front-loaded with a one-sentence summary followed by compact Args, Returns, and Examples sections. Every section adds useful semantic information, and the example input/output pair clarifies expected behavior without filler.

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 paginated list tool, the description covers provider values, workspace semantics, pagination bounds, raw behavior, and the response contract. It lacks explicit error-case or rate-limit notes, but these are less critical for a read-only list operation with an output schema already present.

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 fully compensates by explaining all five parameters: provider allowed values, workspace scope, one-based page, page_size range 1-100, and raw behavior. This adds substantial meaning beyond the bare schema types and defaults.

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 opens with a specific verb and resource: 'List repositories visible to the authenticated provider account.' It clearly establishes the tool's scope and is easily distinguished from the sibling pull-request tools, which operate on a different resource.

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 usage context is implied by the resource name and sibling names, but the description never explicitly states when to choose this tool over list_pull_requests or other alternatives. There is no 'use when...' or exclusion guidance, so an agent must infer applicability.

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