Delete group

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

Annotations already flag the tool as destructive and non-read-only. The description adds meaningful behavioral context by stating that athletes inside the group are not deleted and that the default group cannot be deleted, which are important side-effect constraints not captured in 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?

Two short, direct sentences with no filler. The first sentence states the core action and the key exception (athletes not deleted); the second adds the important restriction about the default group. Every word earns its place.

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 covers all essential aspects: what is deleted, what is preserved, and a critical constraint. The annotations provide the safety profile, so no further return-value or error details are necessary.

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 schema fully documents the single parameter group_id with a description ('Group (tag) ID'). The tool description does not add any additional parameter-level detail, so it stays at the baseline for complete schema coverage.

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 an athlete group') with a specific resource, and immediately clarifies that only the grouping is removed, not the athletes. This distinguishes it from sibling tools like tp_remove_athletes_from_group, which removes members while keeping the group.

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 provides clear context: this tool deletes the group container itself, not the athletes inside it. It does not explicitly name alternative tools for removing athletes, but the implication is clear given the sibling list and the clarifying phrase 'athletes are not deleted.'

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