search_ikea_furniture

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

With no annotations, the description carries full burden but only discloses search criteria and labeling of series matches. It does not mention read-only nature, pagination, or side effects, though these are implied. The output schema may compensate for return format details.

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 plus a blank line, front-loaded with purpose, and every sentence adds value. No waste, highly efficient.

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 8 parameters and no annotations, the description covers the main search dimensions and usage context. The output schema exists, so return value details are external. Could mention query string usage or pagination, but overall adequate for a search tool.

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?

The description references product language and room-fit dimensions (matching parameters like query, max_width_mm) but does not explain each parameter's purpose, defaults, or interaction. Parameter names are self-explanatory, but with 0% schema coverage, the description could add more semantic 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?

The description clearly states the tool searches IKEA furniture by product language and room-fit dimensions, which is a specific verb+resource+criteria. It distinguishes from sibling tools like get_ikea_furniture (single item by ID) and list_ikea_furniture (browse without dimension search) by highlighting the unique search capability.

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 advises using this tool before placing furniture and distinguishes between exact-dimension matches for final layouts and series-only matches for concept design. It does not explicitly mention when not to use or alternatives, but the guidance is clear and contextually useful.

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