pmg_action_delete

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

Discloses mutation, dry-run default, confirmation requirement, and necessary config. Warns about rejection of built-in objects. With no annotations, it covers key behaviors but omits details on success/failure or idempotency.

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 at 7 lines, front-loads purpose and action, no wasted words. Includes a necessary note. Structure is 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?

Given the presence of an output schema, return value details are not needed. Covers purpose, prerequisites, mode of operation, source of ID, and a warning. Missing explicit error handling but sufficient for a simple 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?

Explains id_ format and source (compound ID from pmg_action_objects_list) and confirm usage (dry-run vs execute). Schema coverage is low (33%), so description adds significant value. Proximo_target is already described in 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 it deletes an action object from the PMG RuleDB, using specific verb and resource. It distinguishes itself from sibling tools by being the delete operation among many create/update/list tools.

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 clear guidance: dry-run by default, confirm=True to execute, requires PROXIMO_PMG_* config, and warns to check 'editable' flag before confirming. However, it 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.