delete_dfw_policy

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

Annotations already mark destructiveHint=true. The description adds the specific ValueError condition for active rules, which beyond annotations. It does not mention other side effects, but the key destructive behavior is well-covered.

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?

Four sentences: action, conditional warning, prerequisite, then parameter descriptions. Front-loaded with '[WRITE]' and the verb. No wasted words, well-organized.

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 simple delete operation with 2 parameters and no output schema, the description covers purpose, prerequisite, and parameter meanings. It lacks mention of return value, but for a delete tool that is often implicit.

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?

With 0% schema coverage, the description compensates by explaining that policy_id is the ID and target is optional for NSX Manager target. This is concise but sufficient for both parameters.

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 explicitly states 'Delete a DFW security policy', clearly identifying the verb and resource. It distinguishes from sibling tools like create_dfw_policy, update_dfw_policy, and list_dfw_policies.

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 provides explicit guidance: raises ValueError if policy has active rules, and instructs to delete rules first. This tells the agent when to use (policy empty) and when not to (rules present).

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