pmg_ruledb_rule_when_detach

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

Discloses mutation nature (MUTATION (MEDIUM)), dry-run default, effect of confirm=True, and return format. Clarifies that only the binding is removed and the when-group persists. No annotations provided, so description carries full burden; it is thorough.

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?

Two short, direct sentences plus a clarifying note. Action and risk level are front-loaded. Every sentence serves a purpose. No unnecessary 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?

Covers mutation type, default behavior, side effect (binding only), return format for execution, and related tools for further actions. Output schema exists, so return details not needed. Description is complete for correct invocation.

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%, baseline 3. Description adds value by explaining confirm parameter's dry-run vs execute behavior and return format. It does not repeat schema descriptions for id_ and ogroup but gives context for their role in the operation.

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?

Description clearly states the action: 'detach a 'when' (timeframe) group from a PMG RuleDB rule.' It uses a specific verb (detach) and resource (when group). It also implicitly distinguishes from sibling tools like pmg_ruledb_rule_when_attach and pmg_when_group_delete by stating that only the binding is removed and the group itself remains.

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?

Explicit guidelines: dry-run by default, only removes binding, leaves when-group untouched. Directs to use pmg_when_group_delete for permanent deletion and pmg_ruledb_rule_when_list for listing bindings. Provides clear when-to-use and when-not-to-use context.

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