remove_vm_tag

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

Adds significant context beyond annotations: states that only the exact pair is removed (preserving others), and warns about immediate impact on dynamic security group membership. The idempotentHint and destructiveHint are consistent with the described behavior.

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?

Description is concise with no fluff. Front-loaded with purpose and key behavior, then a bulleted list for parameters. Every sentence adds value, and the structure makes it easy to scan.

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, side effects, parameters, and a prerequisite. Lacks details on return value or error handling, but given no output schema and simple operation, it is mostly complete for agent decision-making.

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%, but the description includes an Args section explaining each parameter with examples and sources (e.g., VM ID from list_vm_tags). This compensates well, though target could have more detail about its origin or default.

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 the action 'Remove an NSX tag from a virtual machine', specifying the resource and verb. It distinguishes from siblings like apply_vm_tag and list_vm_tags by emphasizing that only the exact scope/value pair is removed.

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?

Provides clear context for when to use, including a prerequisite recommendation ('Use list_vm_tags first to confirm the exact scope and value'). Explicitly mentions consequences (changing group membership) but lacks explicit when-not-to-use guidance compared to alternative tools like apply_vm_tag for modifications.

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