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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds important context: branch deletion is allowed only when no classes remain, only the target branch is removed, and owner-level authorization is required. It could go further by stating irreversibility explicitly, but it meaningfully supplements the annotations.

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 two tight sentences with no wasted language. The core action, deletion precondition, scope, and permission requirement are all front-loaded.

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 simple destructive tool with complete schema coverage and relevant annotations, the description supplies the key preconditions and authorization requirement. No output schema is present, but return value details are not necessary for correct invocation.

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 tool has one required parameter and schema description coverage is 100%, so the schema already explains that 'id' is the branch's id. The description does not add parameter syntax or format details beyond what the schema provides, which is the baseline expectation here.

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 states a specific verb and resource ('Remove a branch') and adds a clear scope constraint ('that has no classes left'). It is easily distinguishable from sibling removal tools such as remove_class, remove_fee, and remove_level.

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 gives explicit preconditions: the branch must have no classes left, only that branch is affected, and the caller must be the owner. It does not name an alternative tool, but the context is sufficiently clear for an agent to decide whether to invoke it.

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