Withdraw Item From Container

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the description's mutation behavior is consistent. It adds error cases ('no container open, or item not present') and return shape ('{ message }'), providing useful context beyond 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?

Two-sentence description plus return/error lines, no redundancy. Every sentence adds value: operation, prerequisite, and failure modes.

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?

For a straightforward withdrawal action with clear prerequisites and errors, the description covers the essential operational context. It omits post-withdrawal container state but that is inferable from the schema and sibling tools; not a significant gap.

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 describes count as 'Omit to withdraw the entire stack found' and requires item_name with minLength. The description does not elaborate on parameters, but the tool's purpose makes item_name obvious; count semantics are already in schema. At 50% schema coverage, this is adequate but not exemplary.

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 explicitly states 'Moves an item from the currently open container into the bot's inventory' – a specific verb, resource, and direction. This clearly distinguishes it from siblings like minecraft_container_deposit and minecraft_toss_item.

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?

Mentions prerequisite 'Call minecraft_open_container first' which tells when this tool is valid. Does not explicitly name alternatives but the direction (from container to inventory) contrasts with deposit, making usage context clear.

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