Pick Up Item

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

Annotations are all false, so description carries burden. It says 'try' indicating possible failure but does not detail what happens on success/failure or any side effects.

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?

Single, clear sentence. Front-loaded with action and necessary context. No extraneous words.

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 tool with full schema parameter descriptions, the description completes the picture. Lacks edge-case handling but adequate for its simplicity.

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%, so baseline 3. Description adds that the item must be 'discovered in the room', refining the parameter meaning beyond the schema's description.

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: 'take or pull an item you have discovered in the room.' It specifies the resource (item) and distinguishes from sibling tools like inspect or use.

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?

Implies usage when a discovered item is present in the room. Does not explicitly list when not to use or provide alternatives, but context suggests it's for obtaining items.

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