repository_status

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

The readOnlyHint annotation already provides the key safety trait. The description adds that the tool lists all configured repositories and includes sync error state, which is useful context, but does not address more specific behaviors like pagination or result size limits. No contradiction with annotations.

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?

One clear, front-loaded sentence that states the action first, then lists the output fields. Every word earns its place and there is no 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 zero-parameter, read-only listing tool with a readOnlyHint annotation and an output schema, this description fully communicates what the tool does and what the agent should expect. No critical gaps remain.

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 the schema is empty, so there is no parameter burden on the description. Baseline of 4 is appropriate for a no-parameter tool; nothing further is needed.

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?

Description starts with a clear verb ('Show') and identifies the resource ('every configured repository'), then enumerates the exact fields returned. It is easy to distinguish from sibling tools that search, sync, or reindex.

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 that this tool is for inspecting repository state, but it does not explicitly say when to use it instead of sync_repositories or reindex_repository. The read-only status context is clear but no alternatives or exclusion conditions are stated.

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