list_ikea_furniture

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

With no annotations provided, description carries full burden. It discloses 'compact paginated asset cards' and 'controlled' library, but does not mention permissions, rate limits, or whether listing is read-only. Adequate for a list tool, but room for improvement.

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?

Description is well structured: purpose, args, returns, usage tip. It is relatively concise and front-loaded. Minor redundancy like 'Optional exact category filter' could be tightened, but overall effective.

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?

Covers main purpose and alternative tool, but is incomplete on pagination parameters (limit/offset) and return format. Output schema likely provides details, but description should at least mention standard pagination controls.

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 has 0% description coverage, so description must explain parameters. It only elaborates on 'category' with examples, but does not explain 'limit' and 'offset', leaving two of three parameters undocumented. This is a significant gap.

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 it lists furniture in a specific model library ('controlled IKEA Singapore model library'), and distinguishes itself from sibling 'get_ikea_furniture' by noting that list returns compact paginated cards while get is for full metadata.

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?

Explicitly advises using get_ikea_furniture for a selected asset needing full metadata, implying list is for browsing. However, does not mention sibling search_ikea_furniture or specify when to use list over search, leaving some ambiguity.

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