vmware-nsx-security

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

With no annotations provided, the description carries the full burden. It successfully discloses the ValueError exception condition and the prerequisite dependency on rule deletion. However, it fails to explicitly state that the operation is permanent/destructive or describe what success looks like (return value).

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?

Excellent structure with zero waste: purpose stated first, followed immediately by critical safety warnings (ValueError and prerequisites), then parameter documentation. Every sentence provides essential information for safe invocation.

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?

For a destructive operation with zero annotations, the description covers the critical safety constraint (rule dependencies) but lacks explicit confirmation that deletion is irreversible. No output schema exists, and the description doesn't clarify success indicators, leaving a gap in the complete operational picture.

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 description coverage is 0%, so the description compensates by documenting both parameters: policy_id is explained as 'ID of the policy to delete' and target is clarified as 'Optional NSX Manager target name from config', adding necessary context missing from the raw 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 opening sentence 'Delete a DFW security policy' provides a specific verb and resource. The subsequent mention of 'active rules' effectively distinguishes this from sibling tools like delete_dfw_rule and clarifies the policy/rule hierarchy.

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 states the precondition 'Delete all rules in the policy first before deleting the policy itself' and warns about the ValueError condition. While it doesn't explicitly name delete_dfw_rule as the tool to use first, it provides clear guidance on the required workflow.

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