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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine value by distinguishing the two fulfillment channels queried (home-delivery vs click-and-collect), though it says nothing about response shape or freshness of stock data.

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, zero filler, and the core action is front-loaded ahead of the sibling-routing guidance. Every clause 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?

With annotations covering safety, an output schema handling return values, and full parameter coverage, the description is nearly complete for a single-item lookup. A minor gap is the absence of any note on data freshness or whether multiple fulfillment channels are returned together.

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 item_no and country are already documented including the 'us' default and item-number formats. The description only restates 'one item number' and 'requested country', adding no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (check) and resource (IKEA home-delivery and click-and-collect stock) scoped to one item number in a requested country. It clearly separates itself from siblings like ikea_product and ikea_search, which are framed as item-identification tools rather than stock checkers.

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 names the prerequisite alternatives (ikea_product or ikea_search to identify the item, ikea_stores for locations), giving the agent a routing rule for the surrounding workflow rather than leaving selection to inference.

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