passgage_delete_branch_group

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 simply says 'Delete a branch_group by ID' without mentioning whether the deletion is permanent, if there are any side effects, authorization requirements, or what happens if the branch_group does not exist. This is a significant gap for a destructive operation.

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 sentence that directly states the operation and target. It is appropriately concise with no wasted words, making it easy to parse and understand quickly.

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 delete operation with one parameter and no output schema, the description is minimally adequate. It states what the tool does, but it lacks context about the consequences of deletion, any dependencies, or return values. Since no annotations compensate, the description could do more to fully inform the agent.

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 already provides 100% coverage for the single parameter, including a description of 'id' as the UUID. The description adds no additional meaning beyond 'by ID', so it meets the baseline for full schema coverage without adding extra context.

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 branch_group by ID' clearly states the verb (Delete) and the resource (branch_group), and it distinguishes this tool from siblings like get_branch_group, create_branch_group, and update_branch_group by specifying the delete action and the ID parameter.

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 intended use is implied by the tool name and description: to delete a specific branch_group. However, the description does not explicitly state when to use this tool versus alternatives, nor does it provide any prerequisites or exclusion criteria.

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