pmg_who_group_delete

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

No annotations provided, so description carries the burden. Discloses that it is a mutation, includes a dry-run safety measure, and warns that removing a group also removes all objects within it, which is critical behavioral information. Also mentions the PMG version and API path. Does not cover idempotency or reversibility.

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?

Concise, front-loaded with 'MUTATION (MEDIUM)', includes essential info in a few sentences. Could be slightly more structured, but overall efficient.

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?

There is an output schema, so return values are covered. Description covers behavior, parameters, config requirements, and warnings. Missing error handling details, but sufficient for a delete 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?

Input schema only describes proximo_target. Description adds meaning for ogroup (numeric ID from pmg_who_groups_list) and confirm (execute flag). This compensates for the 33% schema coverage, making the parameters clearer.

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?

Clearly states it deletes a PMG RuleDB 'who' object group, with dry-run by default and confirm to execute. Provides API path. However, does not explicitly differentiate from sibling delete tools for other group types (pmg_when_group_delete, pmg_what_group_delete), though the context is clear.

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?

Describes dry-run and confirm flag, needed config (PROXIMO_PMG_*), and warns about cascading deletion. Does not explicitly state when to use vs alternatives or when not to use. Usage is straightforward for a delete tool.

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