pmg_when_group_delete

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

No annotations provided, so description carries full burden. It discloses mutational, irreversible nature, dry-run behavior, and raw API response on execution. Does not mention permissions, but acceptable for a moderately complex tool.

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?

Highly concise: one-line label and two sentences. No unnecessary words, front-loaded with mutation type and resource.

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 output schema exists (not shown but noted), the description covers primary concerns: dry-run, execution, irreversible, referencing list tool. Minor omission like error handling is acceptable.

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% (baseline 3). Description adds helpful context: ogroup is a numeric ID from pmg_when_groups_list, confirm=True returns specific response. Adds meaning beyond 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 'delete a PMG RuleDB 'when' object group' with a specific verb and resource. It distinguishes from siblings pmg_when_groups_list and pmg_when_object_delete by naming them and contrasting their use.

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?

Provides explicit when-to-use guidance: dry-run by default, irreversible, list groups first, and for removing a single timeframe use pmg_when_object_delete. Also explains confirm=True execution and return format.

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