MiSTerClaw

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

No annotations provided, so description carries full burden. Explains fuzzy search behavior vs exact path matching. However, omits side effects (does it terminate current game?), error behavior (what if ROM not found?), or synchronous/asynchronous nature.

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 tight sentences: first establishes purpose, second details parameter usage. Zero redundancy. Front-loaded with action verb. Every clause earns its place.

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?

Compensates for schema's lack of required fields by explicitly stating XOR constraint. With 3 well-documented parameters and no output schema, coverage is appropriate. Deducted one point for missing side effect disclosure expected for a launch/mutation operation.

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 has 100% coverage, establishing baseline 3. Description adds value with concrete examples ('sonic 2', 'SNES', 'MegaDrive'), clarifies the query/path mutual exclusivity, and emphasizes the system requirement for path usage.

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 specific verb 'Launch' with resource 'game on MiSTer-FPGA' and distinguishes from siblings like 'mister_search' (which only searches) and 'mister_screenshot' (which captures screen). Clearly defines the core action.

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 guides parameter selection: 'Use query for fuzzy search... or path for exact ROM path.' States critical XOR constraint 'Either query or path is required' not enforced by schema. Lacks explicit when-NOT-to-use guidance (e.g., when game already running).

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