repository_list

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

The [READ] prefix hints at read-only behavior, and the description explains the parameter, but it does not disclose any additional behavioral traits such as authentication needs, error handling, or side effects. Without annotations, the description carries the burden but is minimal.

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 extremely concise, with two lines. The purpose is front-loaded with [READ] and the parameter explanation follows. No redundant information.

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?

The description lists the returned fields (id, name, type, path), which is helpful given no output schema. It lacks details on pagination, ordering, or error responses, but overall is sufficient for a simple list tool.

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 coverage is 0%, but the description fully explains the sole parameter 'target': it is a Veeam target name from config, and omitting it uses the default. This adds significant meaning beyond the schema's type definition.

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 clearly states it lists backup repositories with specific fields (id, name, type, path). The [READ] prefix indicates read-only. It distinguishes from sibling tools like repository_get (single repository) and repository_state (state).

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 provides basic usage context (list repositories with optional target parameter) but does not explicitly state when to use this tool vs alternatives like repository_get or repository_state. No exclusions or prerequisites are mentioned.

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