list_repositories

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

With no annotations, the description carries the full burden for behavior. It clearly conveys that this is a listing/read operation and indicates what will be returned, which is adequate for a simple tool. It does not explicitly state that it is read-only, mention side effects, or describe error cases, but for listing repositories the operation is self-evident.

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, well-structured sentence that immediately states the action and the output content. There is no fluff or redundant wording, and all words earn their place.

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 no-parameter list tool with an output schema available, the description covers the essential purpose and expected results. It does not mention scope or filtering, but given the tool's simplicity and the presence of an output schema, nothing critical is missing.

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?

The tool has zero parameters and schema coverage is 100% vacuously, so the baseline for parameter semantics is 4. The description adds no parameter-specific detail, but none is needed since the input schema declares no properties.

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 states a specific verb ('List') and resource ('configured repositories'), and specifies the returned information: paths and architecture metadata. It is unambiguous about its core function. However, it does not explicitly distinguish itself from sibling tools like repository_health, so it stops short of a 5.

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 gives no guidance on when to use this tool versus alternatives. It neither mentions prerequisites nor names siblings such as repository_health or list_tasks that might seem related. An agent must infer usage purely from the name and description, which is acceptable but leaves gaps.

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