MiSTerClaw

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

No annotations provided, so description carries full behavioral burden. It discloses the mechanism (virtual keyboard) but omits critical operational details: whether inputs are queued or immediate, if the device must be in a specific state, or what happens if the key is invalid.

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?

Efficiently structured with the main action in sentence one, followed by three short usage directives. No wasted words. Could accommodate one more sentence for gamepad parameters without sacrificing conciseness.

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?

With five parameters and no output schema, the description covers the keyboard input modes adequately but fails to contextualize the gamepad-oriented parameters, leaving the agent uncertain about the relationship between button/dpad and the 'virtual keyboard' mechanism mentioned.

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?

While the description adds valuable specific values for 'key' (up, down, coin, start) not in the schema and clarifies combo syntax, it completely ignores two of five parameters ('button' and 'dpad'). With 100% schema coverage, the description must compensate for parameter understanding, but leaving 40% of parameters undocumented in the prose is a significant gap.

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?

Clear verb ('Send input') and resource ('MiSTer-FPGA'), distinguishing it from config/read siblings. However, framing as 'virtual keyboard' incorrectly narrows scope since the tool also accepts gamepad 'button' and 'dpad' inputs, creating slight ambiguity.

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?

Excellent explicit guidance on parameter selection: 'Use X for...' pattern clearly maps input types to the correct parameter (key vs raw vs combo). Includes concrete examples (e.g., ['leftalt', 'f12']). Only lacks guidance on when to prefer gamepad parameters (button/dpad) over keyboard.

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