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 one genuine behavioral fact beyond that: omitting project widens the result set to all visible projects rather than erroring. It says nothing about result volume, permissions, or ordering.

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 compact sentence with the resource front-loaded and the conditional scope at the end; no filler. It loses a point for being an elliptical fragment rather than a complete statement of the 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?

An output schema exists, so return values need not be explained, and the one-parameter surface is small. Still, for a tool with an untyped string parameter and no enums, the definition leaves the agent guessing about identifier format and how results relate to browse_repository.

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 carries the full burden for the single `project` parameter, and it does so well by defining both the set case and the unset case (all visible projects). It only lacks detail on accepted project identifier formats (name vs id).

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 resource is unambiguous (Git repositories) and the parenthetical scope clause is useful, but the text is a noun phrase with no verb, so it never states that the tool enumerates/lists repositories. It implicitly separates from browse_repository by scoping to a project level, but does not name any sibling.

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 when-to-use guidance: nothing tells the agent to prefer this over browse_repository, get_file_content, or list_projects, nor any prerequisite for determining a valid project identifier. The only guidance is implicit in the 'if no project is set' clause.

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