pmg_when_object_delete

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

Despite no annotations, description discloses mutation behavior, dry-run default, confirm requirement, and config dependency. It includes the pmgsh-verified path and clarifies the endpoint. Does not detail error handling or rollback but covers essential behavioral traits for a delete operation.

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?

All sentences are essential, with the purpose stated first. The description is compact, covering action, parameters, path, and config without redundancy.

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 an output schema exists, description does not need return values. It covers purpose, parameter sources, and execution flow (dry-run/confirm). Lacks mention of error states or prerequisites like group existence, but overall adequate 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?

With only 25% schema coverage, description adds crucial meaning: it explains ogroup and id_ as numeric strings from specific lists (pmg_when_groups_list and pmg_when_group_objects), and documents confirm and proximo_target. This far exceeds schema alone.

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 it deletes a timeframe object from a PMG RuleDB 'when' object group, using specific verbs and resource. It distinguishes from sibling tools like pmg_when_group_delete by specifying object-level 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?

Indicates dry-run by default and confirm to execute, providing basic usage instructions. However, it does not explicitly mention when to use this tool versus alternatives (e.g., pmg_when_group_delete) or provide exclusion criteria.

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