delete_branch

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

With no annotations provided, the description carries full burden. It clearly warns that deletion is destructive, requires confirm=true, and describes the return behavior (confirmation message or error if confirm not True). Additional details like irreversible effects or permission requirements are missing but the core behavior is covered.

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: a short intro, a prominent warning, usage instructions, parameter list, and return info. Every sentence is meaningful and earns its place, with no redundant content.

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?

Given the destructive nature and presence of an output schema, the description provides essential context: the confirm requirement, default values for repository/workspace, and return type. It could be slightly enhanced by mentioning potential errors or prerequisites but is largely sufficient.

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?

Despite 0% schema coverage, the description includes an 'Args' section that explains each parameter: branch_name, confirm (including the safety requirement), repository, and workspace. This adds significant meaning beyond the raw schema, compensating fully for the lack of schema descriptions.

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 begins with a clear verb+resource statement: 'Delete a branch from a BitBucket repository.' It distinctly separates this from sibling tools like create_branch or get_branch by explicitly naming the action and resource.

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 states when to use: 'Use this tool only when the user explicitly requests to delete a branch and has confirmed the deletion.' It warns about the destructive nature and the confirm parameter but does not mention alternative tools for similar operations.

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