delete_group

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

Adds valuable context beyond annotations: specifies that deletion raises ValueError if group is referenced by a DFW policy rule. This helps the agent anticipate failure conditions.

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?

Short and structured with [WRITE] tag and Args section. No extraneous information, but the Args section could be 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 the main behavioral nuance (referenced group blocking deletion) and parameter names. For a simple delete tool, this is adequate, but lacks return value details (a common omission noted by no output schema).

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?

Briefly lists both parameters (group_id and target) but adds little beyond input schema. Schema has no descriptions (0% coverage), so the description partially compensates but does not clarify format or usage.

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 it deletes an NSX security group, using verb 'Delete' and specific resource. Siblings include create_group and list_groups, so the tool's purpose is distinct.

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?

Implies when to use (deletion) and notes a condition (raises ValueError if referenced), but no explicit alternatives or when-not-to-use. Could mention using update_dfw_rule to remove references first.

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