pmg_ruledb_rule_delete

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

No annotations provided, so description fully discloses behavior: mutation medium severity, dry-run default, permanent removal of rule and group bindings. Also provides API path for verification.

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?

Three efficient sentences with key info front-loaded: action, dry-run, confirm, config, API path, warning. No fluff.

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?

Output schema exists, so return values are covered. Description covers purpose, parameters, safety, and configuration. Missing details on error responses or post-deletion state, but sufficient given the complexity.

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 low (33%), but description adds critical meaning for 'id_' (rule ID as positive integer string) and 'confirm' (triggers execution). 'proximo_target' is already described in schema, so no redundancy.

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 explicitly states 'delete a PMG RuleDB rule' with verb and resource. It clearly distinguishes from sibling tools like pmg_ruledb_rule_create, pmg_ruledb_rule_get, pmg_ruledb_rule_update by specifying the delete action and unique behavior (dry-run, confirm).

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 as default and confirm=True to execute, which guides safe usage. Mentions required config but lacks explicit when-to-use vs alternatives. Warning about permanent removal implies cautious use.

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