mcp-qemu-lab

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that artifacts include 'hashes and provenance', which adds some context about return data, but fails to cover critical aspects like whether this is a read-only operation, if it requires specific permissions, or how results are paginated/formatted. For a tool with no annotation coverage, this is insufficient.

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 action ('List artifacts') and adds clarifying details ('with hashes and provenance') without any wasted words. It's appropriately sized for its purpose and easy to parse.

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 that an output schema exists, the description doesn't need to explain return values, which helps completeness. However, with no annotations, low schema coverage for parameters, and multiple sibling listing tools, the description lacks sufficient context for optimal agent use. It's minimally viable but has clear gaps in usage and behavioral guidance.

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?

The input schema has one parameter ('vm_id') with 0% description coverage, and the tool description does not mention parameters at all. Since schema coverage is low, the description should compensate but doesn't, leaving the parameter undocumented. However, with only one optional parameter, the baseline impact is moderate, warranting a score of 3 for minimal adequacy.

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 verb ('List') and resource ('artifacts') with additional attributes ('with hashes and provenance'), which provides a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'process_list' or 'guest_copy_out', which also list resources, leaving room for ambiguity about when to choose this tool over others.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'process_list' and 'guest_copy_out' that also list resources, there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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