list_stores

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the tool lists stores and describes filter behavior. 'List' implies a read-only operation, and the omit behavior is a meaningful disclosure, though it does not mention auth, output shape, or pagination.

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, front-loaded with the primary purpose, and every word adds value. It avoids unnecessary detail or repetition, making it optimal for quick AI parsing.

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 the tool's simplicity—one optional parameter, no output schema—the description provides all necessary context: what is returned, how filtering works, and the default behavior. It is complete enough for an agent to select and invoke the tool without further clarification.

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 input schema only provides an enum without descriptions, giving 0% schema coverage. The description fills this gap entirely by explaining that countryCode filters by country ('US' or 'CA') and that omitting it returns all stores, adding meaning beyond the raw enum values.

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 starts with a specific verb 'List' plus a clear resource: 'IKEA store IDs and display names'. This clearly distinguishes it from sibling tools that search products or check stock, leaving no ambiguity about what the tool does.

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 states how to use the optional countryCode parameter and what happens when it is omitted ('omit to return all stores'). It provides clear usage context, though it does not explicitly mention when not to use the tool or name alternatives.

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