delete_repository

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

The description prominently warns 'WARNING: This is a destructive operation that cannot be undone.' and explains the safety measure of the confirm parameter. With no annotations, it covers destructive nature and irreversible action.

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 well-structured with warning, usage guidance, args list, and return note. Every sentence adds value with 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 destructive tool, it covers key concerns (irreversible, confirm required) and mentions return type. However, it lacks details on error cases or behavior with invalid inputs, which would be helpful.

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 description carries full burden. It explains each parameter: repository slug, confirm must be true, workspace optional with default. This adds significant meaning beyond the raw schema.

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 'Delete a repository from BitBucket' with a specific verb and resource. It distinguishes from sibling tools like create_repository and update_repository.

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 explicitly says 'Use this tool only when the user explicitly requests to delete a repository and has confirmed the deletion.' It provides clear context for when to use, though it does not mention alternatives or when not to use.

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