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

The annotations already mark this as destructive, but the description goes further by explaining what is NOT destroyed: accounts stay connected, and scheduled posts are unaffected because posts reference accounts rather than groups. This materially helps an agent understand the real-world impact of the deletion.

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 front-loaded with 'Remove a group' and keeps all additional sentences relevant to deletion consequences. It is concise, though the phrase 'only the name and its membership go' is slightly redundant after saying accounts are not touched.

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 with an output schema and strong annotations, the description covers the key context: what is removed, what is preserved, and why posts are safe. It does not specify behavior for non-existent groups, but the idempotentHint partially mitigates that concern.

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 input schema already fully documents the single parameter 'name' with the description 'The group to remove, from groups_list.' The tool description adds no new parameter-level information, so the schema coverage baseline of 3 applies.

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 starts with a specific verb and resource: 'Remove a group.' It also clarifies the scope by stating that accounts are untouched and posts remain unaffected, which distinguishes it from sibling tools like groups_update or groups_create. This is not a tautology; it adds behavioral specificity.

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 the tool should be used when a group needs to be deleted, and it provides helpful cautionary context about side effects. However, it does not explicitly state when to choose this tool over alternatives or mention any conditions where deletion should be avoided.

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