apply_vm_tag

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

The description adds behavioral context beyond annotations: it states the operation is additive and preserves existing tags. Annotations indicate it is not read-only, not destructive, and open-world. The description reinforces this with no contradictions.

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?

The description is concise and well-structured: action line, behavioral note, prerequisite, and parameter explanations. It is front-loaded with the purpose and uses a clear list format for parameters.

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?

The description covers purpose, parameters, and behavior, but lacks information about the return value or success/failure indicators. Since there is no output schema, this omission leaves uncertainty for the AI agent.

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 description coverage, the description fully explains each parameter: vm_id as the external ID, tag_scope and tag_value with examples, and target as optional. This adds significant meaning beyond the type-only 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 description clearly states the action 'Apply an NSX tag to a virtual machine' and uses '[WRITE]' as a verb prefix. It distinguishes from sibling tools like list_vm_tags by explaining that it is additive and provides a prerequisite.

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 specifies when to use the tool (apply tags) and gives a direct prerequisite: 'Use list_vm_tags to get the vm_id first.' It also notes that existing tags are preserved, guiding proper usage. However, it does not explicitly state when not to use it.

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