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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds the meaningful ownership precondition, but says nothing about consequences — what happens to members, invites, or content, and whether the deletion is recoverable.

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?

A single front-loaded sentence with the ownership qualifier placed where it matters and no filler. It is efficient, though the extreme brevity leaves the gaps noted in other dimensions.

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 one-parameter destructive tool whose annotations cover the safety profile, this is borderline adequate, but it omits error behavior when the caller is not the creator and omits any statement of what deletion cascades to.

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 0% for the single group_id parameter; the description does not clarify whether it takes an opaque ID or a group name, or where to obtain it. With one undocumented parameter, the description should have compensated and did not.

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 gives a specific verb+resource ('Delete a group') plus an ownership scope ('you created'), which distinguishes it from the read-only get_group and list_groups siblings. It stops short of naming leave_group, the closest sibling, so the boundary is only partially drawn.

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?

'you created' implies a precondition that the caller must be the group owner, but the description never states what to do when that isn't true — notably that leave_group is the correct tool for groups you merely belong to. Usage is implied rather than explicitly routed.

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