create_group

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

Annotations show write, non-destructive, non-idempotent. Description adds that criteria are ORed and details side effects. No contradiction; adds value beyond annotations.

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?

Well-structured with bullet points, front-loaded purpose. Slightly long but every sentence earns its place. Could be slightly more compact.

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 purpose, all parameters, behavioral logic. No output schema, but return value is implied. Complete for a create tool given complexity and sibling context.

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 has 0% coverage; description fully explains each of 8 parameters with usage details (e.g., tag_scope/value, ip_addresses, segment_paths). Adds crucial meaning.

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?

Starts with '[WRITE] Create an NSX security group' - clear verb and resource. Differs from sibling tools like `delete_group` and `list_groups`.

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?

Explains when to use (create groups with membership criteria). Provides details on criteria combination and parameters but no explicit when-not-to-use or alternatives. Still clear context.

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