mc_screenshot

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

Discloses that capture runs on the render thread, pauses for at most one frame, works while paused, and requires mod and MCP server on the same machine. No annotations are provided, so the description carries full burden and covers it well.

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?

Five sentences, each adding essential information. Front-loaded with core purpose, then behavior, defaults, and requirement. No redundant or unnecessary 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?

Given the simple input schema (two optional params, no output schema), the description is fully complete. It explains capture behavior, usage path, and default rationale. No gaps remain.

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 already describes both parameters with coverage. Description adds value by explaining the defaults and suggesting when to override (higher fidelity). This helps the agent choose appropriate values.

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?

Clearly states it captures the Minecraft client framebuffer as a JPEG and returns its absolute path. Distinguishes from sibling tools like mc_screen_inspect and mc_snapshot by specifying the exact operation and output.

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 guidance on using the Read tool to view the image and notes defaults tuned for low-bandwidth inspection. However, it does not explicitly differentiate when to use this tool over related siblings like mc_snapshot or mc_screen_inspect.

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