Remove a repository from the graph

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does state the operation is 'Irreversible' and that it deletes 'every node', which are key traits. However, it omits other relevant behaviors such as permission requirements, potential side effects on other repositories, and error behavior, so it is only partially transparent.

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: two short sentences that front-load the action and add the crucial irreversibility warning. Every word earns its place, with no fluff or repetition.

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?

This is a simple one-parameter tool with no output schema and no annotations. The description covers the core action and irreversibility, but it does not address potential return values, success/failure reporting, or what happens to related data, leaving some contextual gaps.

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 must compensate for the lack of parameter documentation. The description implies the 'repo' parameter identifies a repository but does not specify the expected format (e.g., name, ID, path) or any constraints beyond the schema's type string. This leaves the parameter semantics underdefined.

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 ('Delete') and the resource ('every node belonging to a repository'), which aligns with the title 'Remove a repository from the graph'. This distinguishes it from sibling tools like list_repos and index_repo.

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. The only hint is 'Irreversible', which is a warning but not a usage guideline. No prerequisites, exclusions, or comparison with sibling tools are given.

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