Disconnect from Minecraft World

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

Annotations already provide idempotentHint=true and destructiveHint=false, and the description reinforces idempotent safety by saying it is safe if not connected. The word 'cleanly' adds a subtle behavioral promise, but no new side effects or prerequisites are disclosed beyond what annotations already imply.

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 short sentences immediately convey the purpose and the key safety trait, with no unnecessary words. The information is front-loaded and every sentence 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?

Given the tool's simplicity (no parameters, no output schema), the description completely covers what the agent needs to know. The combination of description and annotations is sufficient for a disconnect action without any clear gaps.

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?

The tool has zero parameters, so the description is not required to explain any parameter details. The baseline of 4 is appropriate because the schema already covers everything (100% coverage) and there are no params to clarify.

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 clearly states the action ('disconnects') and the resource ('current world/server'), and the phrase 'cleanly disconnects' distinguishes it from sibling tools like connect and stop. It also adds a helpful safety note, making the purpose unambiguous.

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?

The description notes that it is safe to call even if not connected, which implies it can be used as a cleanup step, but it does not explicitly mention when to prefer this over minecraft_stop or minecraft_connect. No alternatives or exclusions are given, leaving some inference to the agent.

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