pmg_who_group_update

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

No annotations provided, so description carries full burden. It discloses mutation severity (MEDIUM), dry-run default, confirm flag, config requirement, and partial update behavior. Could mention error handling or permissions, but sufficient for a mutation tool.

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?

Four focused sentences, front-loaded with key info, no unnecessary words. Efficient and well-structured.

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?

With output schema present, return values need no explanation. Covers purpose, usage, parameter details, and behavior. Lacks error handling details but adequate for the tool's 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 only 14%, but description adds meaning: explains ogroup as numeric ID from list, confirm flag purpose, and non-None field behavior. Compensates well for 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 'update a PMG RuleDB 'who' object group config' with a specific verb and resource. It also adds context like dry-run default and confirm flag, and the mention of 'who' distinguishes it from sibling what/when group update 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 explicit guidelines: dry-run by default, confirm=True to execute, needs PROXIMO_PMG_* config, and non-None fields behavior. Does not explicitly exclude other operations like create/delete, but the update purpose is clear.

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