pmg_what_group_delete

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

Discloses that deletion is irreversible and removes every object within the group. Describes dry-run behavior and execution response. Since no annotations exist, the description provides necessary behavioral context.

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?

Three concise sentences, front-loaded with purpose, then key details. No unnecessary words. Well-structured for quick comprehension.

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 all essential aspects: purpose, prerequisites (list groups), alternative tool, irreversibility, dry-run/execution mode, and return format. Output schema existence supplements return details. Comprehensive for a deletion tool.

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 coverage, baseline is 3. Description adds value by explaining ogroup parameter source (from pmg_what_groups_list), confirm parameter dry-run vs execution, and proximo_target's purpose for multi-target config. This enhances understanding beyond the schema.

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 deletes a PMG RuleDB 'what' object group. It uses a specific verb and resource, and distinguishes itself from siblings like pmg_what_object_delete and pmg_what_groups_list.

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?

Explicitly states dry-run by default, advises listing groups first with pmg_what_groups_list, and directs to pmg_what_object_delete for single object removal. Also explains how to execute with confirm=True.

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