Use Item

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond that. It does not disclose potential side effects like item consumption, state changes, or failure conditions, relying entirely on annotations which are incomplete for a game action.

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?

A single, straightforward sentence with no extraneous information. Every word is necessary and earned.

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 potentially complex action (using an inventory item on a room object), the description lacks crucial details such as prerequisites (item in inventory, target visible), outcomes (success/failure), and side effects (item consumption). With no output schema, more explanation is needed for an AI agent to invoke correctly.

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% with clear descriptions for all three parameters (session_id, item, target). The description adds no additional semantic value; baseline score of 3 applies since the schema already does the heavy lifting.

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 verb 'use', the resource 'item from your inventory', and the target 'room object'. It effectively distinguishes from sibling tools like 'pick_up' (taking items) and 'inspect' (examining objects).

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?

No explicit guidance on when to use this tool vs. alternatives. The description implies usage when combining an item with a room object, but does not mention prerequisites, exclusions, or alternative tools for scenarios like examining ('inspect') or moving items ('pick_up').

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