delete_group

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

With no annotations, the description carries the full behavioral burden. It discloses a key side effect: users themselves persist and only lose permissions derived from the group. This goes beyond the basic action and provides valuable context, though it doesn't mention other consequences like irreversibility or auth requirements.

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 concise, front-loaded with a clear action statement, adds a necessary behavioral clarification, and documents the parameter in a single line. Every sentence earns its place, with no redundant information.

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?

The tool is a simple delete operation with one parameter, and the description covers the essential behavior and side effects. The existence of an output schema means return values don't need elaboration. It misses nothing critical for most use cases.

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 description says 'group_id: group ID', which merely restates the schema's parameter name and type without adding meaningful detail. Since schema description coverage is 0%, the description was expected to compensate but fails to provide any additional guidance on the parameter's value or sources.

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 explicitly states 'Delete a group' with a specific verb and resource, and clarifies that users remain but lose permissions, distinguishing it from sibling tools like remove_user_from_group or update_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 implies when to use this tool by explaining the effect on users (they lose permissions but aren't deleted), but it does not explicitly mention alternatives or when not to use it. The usage context is implied rather than stated.

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