minecraft_craft

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal prerequisites: items must be in inventory and a crafting table may be required. However, it does not explain whether materials are consumed, what happens on failure, or whether crafting is blocked when the table is absent.

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 a single compact sentence that front-loads the action and includes only relevant contextual details. Every phrase earns its place, and there is no redundant or vague filler.

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 simple two-parameter action with no output schema, the description gives the core operation and its main prerequisites. Still, it omits count semantics, failure behavior, and how item names should be specified, so an agent would need to infer or experiment to call it reliably.

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 description coverage is 0%, so the description must compensate for sparse parameter documentation. It only implies that 'item' is the thing being crafted and says nothing about 'count,' valid item identifiers, or how count affects the crafting operation.

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 uses a specific verb, 'Craft,' with a clear resource, 'an item,' and adds meaningful scope by mentioning current inventory and a nearby crafting table. This makes it immediately distinguishable from sibling actions like place, collect, or equip.

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 implies the use case: craft an item from current inventory, using a nearby crafting table when the recipe requires it. However, it does not explicitly state when not to use this tool or direct the agent to alternatives such as minecraft_collect or minecraft_place.

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