pmg_when_group_create

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

With no annotations, the description carries the full burden. It discloses mutation severity, dry-run behavior, API path, return value, and dependency on PROXIMO_PMG_* config. It does not mention error handling or reversibility, but covers major behavioral aspects.

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 a single concise paragraph, front-loaded with key info (MUTATION, dry-run, API path). It efficiently lists parameters and their roles without 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?

Given the tool's moderate complexity and presence of an output schema, the description covers purpose, parameters, usage, auth, and output. It could add context about relationships to other PMG objects, but is largely complete for a creation 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?

Schema coverage is low (17%), but the description adds meaning for most parameters: explains 'and_' maps to API 'and', 'confirm' for dry-run, and 'invert' semantics. It omits 'proximo_target', but overall enhances understanding beyond the 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 the verb ('create'), the resource ('PMG RuleDB 'when' object group'), and distinguishes from sibling tools like pmg_when_group_delete or pmg_when_group_get. It also provides the API path, making the purpose unambiguous.

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 mentions the dry-run default and the need for 'confirm=True' to execute, plus the configuration requirement. It does not explicitly compare to alternative tools or specify when not to use, but the context is clear for a creation operation.

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