create_group

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

Annotations already indicate the mutation and non-idempotency, and the description adds that it returns the created group dict and explains how criteria combine and which member types match. It does not mention duplicate-handling behavior, but given the annotation coverage, the additional context is solid.

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 well-structured and concise: it front-loads the purpose, adds the critical condition semantics, then lists parameters compactly. Every sentence earns its place, and the Args block is informative without being bloated.

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 high parameter count, zero schema descriptions, and no output schema, this description is remarkably complete. It covers the return value, parameter meanings, membership matching semantics, and the tool's role in the DFW rule creation workflow, enabling 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?

The input schema provides zero parameter descriptions, so the detailed Args list is essential. The description gives types, constraints, examples, and semantic explanations for every parameter, such as group_id format and ip_addresses as IP/CIDR lists, fully compensating for the schema coverage gap.

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 opens with '[WRITE] Create an NSX security group with optional membership criteria,' which clearly states the action and resource. It is immediately distinguishable from sibling tools like list_groups, get_group, and delete_group, as well as from create_dfw_policy and create_dfw_rule.

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 explicitly says 'Use it before create_dfw_rule, which references the group path; confirm members with get_group,' providing direct strategic workflow guidance. It also explains the OR/AND semantics for membership criteria, which is essential for correct use versus other tools.

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