qemu_type

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

Annotations already declare destructive=true, readOnly=false and idempotent=false, so the safety profile is covered. The description adds genuinely new behavior: US keyboard layout only, shifted symbols supported, '\n' translates to Enter, and a documented failure mode (dropped characters during early boot) with the remedy. It stops short of saying that repeating the call types the text again.

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?

Front-loaded with the core action, then constraints, then parameter tuning — nothing superfluous. The escaped-quote rendering of the newline instruction ('"\n" presses Enter') is slightly garbled and costs a bit of readability.

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?

An output schema exists, so return values need not be described, and annotations cover the risk profile. Combined with the layout/keystroke/failure-mode detail, the definition is nearly complete for a typing tool; only the meaning of the required 'name' argument is left unexplained.

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 description coverage is 0%, so the description carries the burden, and it does well for two of three params: text semantics (layout, shifted symbols, newline behavior) and delay_ms (gap between keystrokes, default tuning advice, must be non-negative). The required 'name' parameter is never explained, which is the main remaining ambiguity.

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?

States a concrete verb and resource ('Type text into the guest as keyboard input') and implicitly separates itself from the sibling qemu_key by operating on whole text rather than single keys. It does not name qemu_key explicitly, so the differentiation is inferred rather than stated.

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?

Usage context is implied (typing strings rather than individual keystrokes) and there is useful conditional advice for delay_ms ('raise it ... if the guest drops characters during early boot'). However, it never explicitly says when to prefer qemu_key or qemu_serial_send, and gives no when-not guidance.

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