hostodo_set_vm_exec_enabled

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

No annotations provided, so description carries full burden. Discloses scope requirement and confirmation format, but does not mention side effects, error handling, rate limits, or whether operation is reversible.

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?

Two concise sentences: first gives action and requirements, second adds parameter specifics. No wasted words, information front-loaded.

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 no output schema and 3 params, description covers purpose, requirements, and parameter details. Could mention what happens on invalid confirmation or whether success is returned, but overall adequate.

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 coverage is 67% (2 of 3 params have descriptions). Description adds crucial context: vm_id must be instance id, confirmation must be exact phrases with examples. Does not add semantics for the enabled boolean beyond 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?

Description clearly states verb 'Enable or disable' and resource 'MCP/QEMU guest-agent root command execution for one owned VPS', distinguishing it from sibling tools like hostodo_exec_vm_command or hostodo_power_vm.

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?

Explicitly states required scope (vms:exec) and exact confirmation phrases for both enable and disable. Also clarifies to use instance id not hostname. Does not explicitly exclude alternative tools but provides clear context.

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