delete_group

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

No annotations exist, so the description must carry the full burden. It discloses that tickets become unassigned, which is a crucial side effect. However, it does not mention other behavioral aspects like irreversibility, required permissions, or deletion of related data (e.g., group settings).

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?

Two sentences, no redundant words. The critical information (action, resource, side effect) is front-loaded. Every sentence 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?

Given the tool's simplicity (single parameter, no output schema, no nested objects), the description covers the main behavioral effect (unassignment). It is complete for typical agent use, though it could mention that the deletion is permanent.

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 coverage is 100% (one parameter with a description). The tool description does not add information beyond the schema's 'Group ID to delete'. The schema already handles parameter meaning adequately, so the description contributes no extra value for this dimension.

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 clearly states the tool's action ('Delete an agent group') and specifies the primary resource, distinguishing it from other delete tools (e.g., delete_article) and group-related tools (create_group, update_group). It also mentions a key side effect (ticket unassignment), adding 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 when to use the tool (when deletion is desired) but does not explicitly state when not to use it or suggest alternatives (e.g., updating group status or archiving instead). No guidance on prerequisites or context is provided.

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