pmg_action_delete

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

Discloses that the operation is irreversible, that PMG rejects deletion of non-editable system objects, and explains the dry-run default versus execution behavior. However, it does not describe the dry-run return format (e.g., what a PLAN looks like), which is a minor gap. With no annotations, the description carries full burden and does well overall.

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 two sentences long, front-loads the main action and mutation type, and includes all critical information. No redundant words.

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 complexity of PMG action objects and many sibling tools, the description provides sufficient context: how to safely delete (check editable flag, use dry-run first), and what to expect on execution. Output schema exists so return values are covered.

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%, so baseline is 3. The description adds value by explaining the 'confirm' parameter's role (dry-run vs execute) and instructing that 'id_' should be obtained from pmg_action_objects_list. It does not describe 'proximo_target', but that parameter is self-explanatory via schema and the context of multi-target setup.

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 an action object from the PMG RuleDB', specifying the verb (delete) and resource (action object). It also distinguishes itself from siblings like pmg_action_objects_list and pmg_action_bcc_create by including the mutation label and mentioning the compound ID source.

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 guidance: dry-run by default, use confirm=True to execute, and advises checking the 'editable' flag via pmg_action_objects_list before attempting deletion of built-in objects. This helps the agent decide when and how to use the tool correctly.

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