resolve_item

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

Describes the conversion process and return format (names, types, rooms, live states), but lacks explicit statement on side effects or read-only nature, though it is implied as a search tool.

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 with no filler; first sentence states primary purpose, second provides usage instruction and examples. Efficient and front-loaded.

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?

Complete for a single-parameter search tool; describes return value (ranked matches with attributes) compensating for lack of output schema.

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?

Gives concrete examples ('kitchen light') and explains the 'query' parameter expects natural-language intent, adding significant value beyond the schema's type definition.

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?

Clearly states it is a 'PRIMARY item finder' that converts natural language into ranked matches with specific attributes, distinguishing it from sibling search tools like query_items.

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 explicit instruction to 'Call this BEFORE any other search', guiding agents on when to use it, though it does not list exclusions or alternatives.

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