pmg_ruledb_rule_action_detach

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

The description labels it as MUTATION (MEDIUM), explains the dry-run default with confirm flag, and notes that it only affects mail flow if the rule is active. Given no annotations, the description adequately discloses behavioral traits beyond the mutation type.

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 concise (5 sentences), front-loads the main action, and provides essential details without redundancy. Every sentence adds value.

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 tool's complexity (mutation with side effects), the description covers the dry-run mechanism, confirmation flag, config requirement, API path, and condition for effect on mail flow. Output schema exists, so return details are not needed.

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?

The schema has 25% description coverage (only proximo_target described). The description adds meaning for id_ ('rule ID') and ogroup ('numeric action group ID to detach'), which are the two required parameters. This compensates for the low schema coverage.

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 the tool's purpose: 'detach an action group from a PMG RuleDB rule.' The verb 'detach' and resource are specific, and it distinguishes from siblings like pmg_ruledb_rule_action_attach by implying removal. The dry-run detail adds clarity.

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?

The description explains the default dry-run behavior and that confirm=True executes the action. It mentions required config (PROXIMO_PMG_*) and provides the API path. It does not explicitly state when to use this tool over alternatives, but the context is clear for detaching an action group.

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