Connect to Minecraft World

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

The description discloses behavioral details beyond annotations: it must precede all other minecraft_* tools, returns a confirmation message with spawn position, and lists specific error conditions (connection refused, wrong port, version mismatch, auth-mode mismatch). It also explains the consequence of choosing the wrong auth mode, which is not encoded in the annotations.

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?

The description is front-loaded with the core operation, followed by practical auth and LAN instructions, then a succinct return/error summary. Every sentence adds a distinct piece of information; the length is justified by the tool's complexity.

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?

The tool has no output schema, but the description covers return values and common error cases. Given the complexity of authentication modes and prerequisite ordering, the description provides all necessary context for an agent to use this tool correctly and distinguish it from the many sibling tools.

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%, but the description adds contextual meaning: it maps auth='offline' to TLauncher/cracked/LAN servers and auth='microsoft' to online-mode servers, explains how to obtain host and port from a LAN world ('host="localhost"'), and notes port is shown in chat. It also clarifies that version can be omitted for auto-detection.

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?

The description states 'Connects the bot to a running Minecraft Java Edition world' and enumerates specific connection targets (server, LAN world, local server jar). This clearly differentiates it from sibling tools like minecraft_disconnect and minecraft_status, which serve different functions.

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?

It explicitly states 'Must be called before any other minecraft_* tool', providing a clear prerequisite. It also gives conditional guidance on auth mode ('Use auth="offline"' for TLauncher/cracked/LAN, 'auth="microsoft"' for real accounts) and step-by-step instructions for connecting to a singleplayer world via Open to LAN.

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