MiSTerClaw

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

No annotations provided, so description carries full burden. 'Rescan' and 'detect' imply state modification (updating library index), but lacks disclosure on duration, synchronicity, handling of removed games, or return value indication.

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 efficiently structured sentences. First establishes purpose, second covers optional parameter usage. No redundant or wasted text.

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?

Appropriate for a single-parameter tool with complete schema coverage. Adequately describes the operation domain, though could improve by noting if the operation is synchronous or what success indicates given no output schema exists.

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 coverage is 100% with complete parameter documentation. Description reinforces the 'location' parameter semantics ('scan only one drive') but adds no new semantic information beyond the schema's examples and optional nature.

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 specific verb 'Rescan' with resource 'ROM library' and scope 'to detect new games'. Effectively distinguishes from sibling 'mister_search' (querying existing library) and 'mister_launch' (running games).

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?

Implies usage context ('detect new games' suggests use after adding ROMs), but lacks explicit 'when to use vs alternatives' guidance. The second sentence provides parameter-level usage, not tool-selection guidance.

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