delete_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 explicitly warns 'There is no confirmation and no undo' and states that deletion is immediate. This is critical for a destructive operation and is transparent about the irreversibility and scope.

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 three short sentences, each earning its place: the action, the warning about no undo, and the scope (measurements not deleted). It is front-loaded with the primary action and contains 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 simple single-parameter delete tool without an output schema, the description covers the necessary context: it identifies the target by UUID, emphasizes the irreversible nature, and clarifies that measurements survive. This is sufficient; no return value is expected for such a command.

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 100% for the single 'group' parameter, which already states 'Group UUID (from list_groups or create_group)'. The description adds little beyond the schema, merely repeating 'by UUID'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the action 'Delete one measurement group by UUID' with a specific verb and resource. It distinguishes itself from sibling tools by clarifying that only the group is deleted, not its measurements, which sets it apart from delete_measurement.

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 when to use this tool: when you want to delete a group but keep its measurements. It does not explicitly name alternatives, but the clarification that measurements are not deleted serves as an implicit distinction from delete_measurement. No explicit exclusions are given.

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