delete_group

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

The description adds 'WARNING: This is irreversible,' which goes beyond the destructiveHint=true annotation by emphasizing permanence. This is useful context for the agent to make risk-aware decisions. It does not contradict the annotations.

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 a single clear sentence plus a concise warning. It is front-loaded with the action and resource, and every word earns its place.

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 simple delete operation with an output schema and clear annotations, the description is nearly complete. It captures the essence (delete by ID, irreversible) and relies on the schema for parameter semantics. It does not mention that confirm must be true, but the schema explicitly covers that.

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 schema already documents all three parameters, including the meaning of group_id ('array index from search_groups'), confirm, and dry_run. The description adds no additional parameter-level detail beyond the schema, so it meets the baseline for high schema coverage.

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 action ('Delete'), the target resource ('pfSense user group'), and the identifier ('by ID'). It is specific and distinguishes this tool from sibling tools like update_group or search_groups.

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 usage for deleting a group, but does not explicitly mention when to use this tool over alternatives (e.g., update_group) or any prerequisites. No exclusions or alternative tool references are provided.

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