buddypress_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 but offers minimal information. 'Delete a group' implies a destructive, irreversible operation, but doesn't specify permissions required, whether deletion can be undone, what happens to group members or associated content, or any confirmation/validation steps. For a destructive operation with zero annotation coverage, this is critically inadequate.

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 extremely concise at just three words, with no wasted language. It's front-loaded with the core action and resource. While it may be too brief for adequate functionality disclosure, from a pure conciseness perspective, every word serves a purpose.

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 destructive deletion tool with no annotations and no output schema, the description is severely incomplete. It doesn't address critical context like what constitutes successful deletion, error conditions, permissions required, side effects on related data, or what the tool returns. The minimal description fails to provide the necessary context for safe and appropriate use of this potentially destructive operation.

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?

With 100% schema description coverage and only one parameter ('id' with description 'Group ID'), the schema fully documents the parameter. The description doesn't add any parameter information beyond what's in the schema, but with complete schema coverage and minimal parameters, a baseline of 4 is appropriate as the description doesn't need to compensate for schema gaps.

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 group' clearly states the verb (delete) and resource (group), making the basic purpose understandable. However, it doesn't distinguish this tool from sibling deletion tools like 'buddypress_delete_activity' or 'buddypress_delete_friendship' - it only specifies what type of resource is being deleted without clarifying what makes group deletion unique compared to other deletion operations.

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 no guidance on when to use this tool versus alternatives. With multiple sibling tools available (including 'buddypress_list_groups' for viewing groups and 'buddypress_update_group' for modifying them), there's no indication of prerequisites, when deletion is appropriate versus modification, or what happens to related data when a group is deleted.

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