vm_set_ttl

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

Discloses daemon requirement for deletion, persistence in ~/.vmware-aiops/ttl.json, and optional target. Annotations confirm write and not read-only, description adds critical behavioral context.

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?

Concise: one sentence for purpose, two for prerequisites/persistence, then parameter list. No unnecessary words.

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, prerequisites, parameters, and persistence. Could mention return value or behavior when daemon is not running, but overall sufficient.

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?

Input schema has 0% description coverage; description fully explains all three parameters, including minimum value for minutes and optional nature of target.

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?

Clearly states the tool sets a TTL for a VM leading to auto-deletion. Distinguished from sibling tools like vm_cancel_ttl and vm_list_ttl.

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?

Mentions prerequisite (daemon must be running) and persistence file. Does not explicitly state when to use this vs alternatives, but context implies setting TTLs.

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