delete_git_repo

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a deletion operation, which implies destructive action, but does not disclose irreversibility, effect on repository files, permissions required, or any consequences. This is a significant gap 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 of six words that directly states the tool's purpose. Every word earns its place, with no redundancy or 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?

This is a destructive mutation tool with no annotations and no output schema. The description explains what the tool does but lacks essential context about side effects, reversibility, success/failure behavior, or prerequisites. While the schema is complete, the overall tool definition is not adequately informative for a delete operation.

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 input schema has 100% coverage with a single parameter 'repository_root' described as 'Repository path to delete'. The tool description adds no additional parameter-specific meaning beyond what the schema already provides. Baseline 3 applies due to high schema coverage.

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 'Delete a Git repository from cPanel' uses a specific verb (delete), identifies the resource (Git repository), and scopes it to cPanel. This clearly distinguishes it from sibling tools such as create_git_repo, update_git_repo, and deploy_git_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 implies usage context but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It is clear this is the deletion operation for Git repos, but there is no mention of situations where deletion might be inappropriate or require additional steps.

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