MiSTerClaw

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

No annotations provided, so description carries full burden. Discloses return format ('PNG image') which is critical behavioral context. However, omits explicit safety confirmation (read-only/destructive status) and timing characteristics that would help an agent decide invocation confidence.

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?

Three tightly constructed sentences with zero redundancy: action sentence, return-value sentence, use-case sentence. Information is front-loaded and 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?

Adequately covers the tool's function despite missing output schema by explicitly stating the PNG return format. Given zero parameters and low complexity, the description provides sufficient context for correct invocation, though explicit safety traits would improve completeness.

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?

Input schema contains zero parameters. Description appropriately requires no parameter explanation, meeting the baseline score for zero-parameter tools.

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?

Specifies exact action ('Take a screenshot') and target ('what's currently displayed on MiSTer-FPGA'), clearly distinguishing from siblings like mister_launch, mister_input, and config tools. The PNG format mention further clarifies the output type.

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?

Provides concrete use cases ('seeing what game is running', 'verifying a launch succeeded') that establish when to invoke the tool relative to mister_launch. Lacks explicit 'when not to use' or alternative recommendations, but the context is clear.

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