inventory

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

No annotations provided, so description covers the merging behavior and the by_container option. However, it does not disclose read-only nature, performance implications, or any side effects. Adequate but could be more transparent.

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 sentences, no filler. Essential information is front-loaded. Every word 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 modest complexity (3 boolean params) and no output schema, the description adequately covers functionality. Could mention what the output looks like, but not strictly necessary.

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 100%, so baseline is 3. The description adds context for by_container (merging vs breakdown) but not for full or save_path beyond what schema already provides. Minimal added value.

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?

Description clearly states the tool retrieves items from player backpack and chests, with two modes (merged and per-container). It implicitly distinguishes from sibling tool 'chests' by covering both backpack and chest contents.

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?

Provides guidance on when to use by_container parameter, but no explicit when-not or alternatives among the 50 sibling tools. Could be improved by mentioning that for per-container breakdown, use by_container or else default merged view.

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