pmg_what_group_delete

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

With no annotations, the description discloses the mutation nature, dry-run default, and importantly warns about cascading deletion of all objects within the group. It also mentions the API path and config dependency, providing clear 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?

The description is concise (6 lines), front-loads the purpose with 'MUTATION (MEDIUM): delete...', and every sentence adds value (warning, path, config requirement). No unnecessary text.

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 complexity and presence of output schema, the description covers the action, parameters, side effects, prerequisites, and even the API path. It is fully informative for an AI agent to use correctly.

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 description adds significant meaning to the ogroup parameter (numeric ID from list) and confirm (execution flag). With only 33% schema coverage, it compensates well, though the proximo_target parameter is not elaborated beyond the schema description.

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 resource ('PMG RuleDB 'what' object group'), and provides specific details like dry-run default and API path. It distinguishes from sibling tools (create, update, etc.) by focusing on deletion.

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 explains the dry-run behavior and confirm flag, and mentions config prerequisites. It implies when to use (delete) but does not explicitly state when not to use or list alternatives.

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