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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond that: it discloses that geo, hours, and price range are only present for full/small stores while order points and pick-up-only points return address only. No auth or rate-limit detail, but the conditional-return behavior is valuable.

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, front-loaded with the resource and its fields, then the parameter provenance and the return-condition caveat. Every clause earns its place with no filler.

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 an output schema present, the description needn't restate return shapes; it instead covers the non-obvious gaps (where slug comes from and why some stores return only an address). Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuine provenance for slug (IKEA's own store URL slug from an ikea_stores result), which the schema only illustrates with an example. Country/language add nothing beyond the schema.

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+resource ('One IKEA physical location's full detail') and enumerates the fields returned (address, geo, hours, price range). It is clearly distinguishable from the sibling ikea_stores list endpoint by scoping to a single location.

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?

Explains the dependency workflow by stating slug is 'taken from an ikea_stores result's own slug field', which tells the agent it must first call ikea_stores. No explicit when-not or alternative-selection conditions are given beyond that, so it stops short of a 5.

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