mcp-qemu-lab

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'unsafe override' which hints at security implications, but doesn't explain what makes commands unsafe, what authentication is required, rate limits, or what happens during execution failures. The SSH aspect is mentioned but not elaborated.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place - 'Execute' (action), 'allowlisted guest command' (resource), 'over SSH' (method), and 'optional unsafe override' (key capability). No wasted words or redundant phrasing.

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?

For a complex execution tool with 6 parameters, 0% schema coverage, no annotations, but with an output schema, the description is insufficient. It doesn't explain the security model ('allowlisted'), SSH connection details, error handling, or what the unsafe override entails. The output schema existence helps, but the description leaves critical gaps for safe usage.

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 for 6 parameters, the description fails to compensate. It only vaguely references 'unsafe override' without explaining the relationship between unsafe_allow_arbitrary_commands and unsafe_command parameters. No parameter meanings, formats, or constraints are provided beyond what's in the bare 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 ('Execute') and resource ('allowlisted guest command over SSH'), making the purpose understandable. It distinguishes from siblings by focusing on command execution rather than debugging, file operations, or VM management. However, it doesn't specify what 'guest' refers to (VM guest OS) or what 'allowlisted' means in practice.

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 mentions 'optional per-call unsafe override' which hints at an alternative mode, but provides no guidance on when to use this tool versus alternatives like guest_copy_in/out for file operations or debugger tools for debugging. No explicit when/when-not instructions or sibling tool comparisons are included.

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