Remove Repositories

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

No annotations are provided, so the description carries the full burden. It states the action but does not disclose whether removal is destructive, whether missing paths cause errors, whether changes are persistent, or how it affects other tools like list_repos. This is minimal transparency for a mutation tool.

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, compact sentence that is front-loaded with the action and target. Every word is relevant, and there is no verbosity or unnecessary detail.

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 tool is simple with one fully described parameter and an output schema present (though its content is unknown). However, the description lacks context about the tool's effects on the configuration, success/failure behaviors, and prerequisites. For a mutation tool with no annotations, more contextual info would be expected, but the simplicity of the operation keeps this at a satisfactory level.

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 schema has 100% coverage with the parameter described as 'Repository paths to remove'. The description echoes this exactly, adding no new meaning. Baseline is 3 for full schema coverage, and the description doesn't compensate beyond that.

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 the action ('Remove') and the specific resource ('repository paths') with scope ('from the configuration'). This distinguishes it from sibling tools like add_repos and list_repos.

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 no guidance on when to use this tool versus alternatives, such as add_repos or list_repos. There is no mention of complementary tools or explicit context for when removal is appropriate.

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