find_item

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

No annotations are provided, so the description bears full burden. It states the search scope and return structure (quantity, container location), but omits critical behavioral details like read-only nature, performance implications, side effects, or what happens if the item is not found.

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 two sentences, each with clear purpose: first defines action and scope, second describes return format and intent. No superfluous 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?

Given no output schema and no annotations, the description provides a reasonable outline of return values (quantity and location) but lacks detail on result structure, error handling, or pagination. For a search tool, this is adequate but not comprehensive.

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 no additional semantics beyond the schema, which already details 'name', 'fuzzy' (substring match), and 'save_path' (with path guidance).

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 'locate', the resource 'item', and the scope 'across player backpacks, all chests, and machine outputs', directly answering 'where is my X?'. This purpose is well-distinguished from sibling tools like 'inventory' and 'chests'.

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 usage for finding a specific item's location via 'where is my X?', but lacks explicit when-to-use, when-not-to-use, or comparisons to alternatives. Sibling tools like 'how_to_obtain' suggest different use cases, but no direct guidance is given.

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