delete_group

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

Adds substantial context beyond the annotations: members retain accounts but lose memberships and anything shared with the group, admin-group protection, and the authorization requirement. This tells the agent exactly what collateral damage to expect from a destructiveHint=true operation.

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?

Front-loaded with the core action, then behavioral notes, then an Args/Returns block. Efficient, though the 'Returns: Confirmation message.' line is partly redundant given an output schema exists.

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?

Covers authorization, protected targets, and member/shared-item side effects for a destructive single-param operation, and an output schema handles return values. Nothing an agent needs to invoke it safely is missing.

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%, so the description must carry the parameter meaning, and it only offers 'The group ID to delete' for group_id. That confirms intent but adds little beyond the self-evident name; the description compensates minimally for the coverage gap.

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?

Opens with a specific verb+resource ('Delete a group') and immediately differentiates from siblings like list_groups, create_group, and delete_user by scoping the action to a group. An agent knows exactly what this operates on without reading the schema.

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?

States prerequisites (admin rights or delegated user administration) and an explicit exclusion ('admin' group cannot be deleted), which is strong when-to-use/when-not guidance. It stops short of naming alternatives (e.g., leave_circle, remove_circle_member, remove_participant) for related removal semantics.

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