get_product_details

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states it 'gets' details, implying a read-only operation, but does not disclose any potential side effects, authentication requirements, rate limits, or what exactly 'details' includes. The lack of any behavioral caveats leaves the agent to infer the operation's behavior.

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 a single, concise sentence that is front-loaded with the core action. It is appropriately sized for the tool's simplicity, and every word adds value without redundancy.

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?

The tool has 3 parameters and no output schema or annotations. The description is minimal and does not cover the role of langCode/countryCode, return format, or any potential errors. For a tool with multiple parameters, this is insufficient context. Sibling tool distinctions are only implied, not explicitly stated.

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 0%, so the description must compensate. It explains that itemNo is used to look up the product, but langCode and countryCode are not mentioned at all. The description adds no meaning for these parameters, leaving the agent to guess their purpose (e.g., localization, currency).

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's purpose: 'Get details for a single IKEA product by item number.' It specifies a verb ('Get'), a resource ('details for a single IKEA product'), and the input method ('by item number'). This distinguishes it from sibling tools like search_products (searching) and list_stores (stores).

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 implies use when you have a specific item number and want product details, but it does not explicitly state when to use this tool versus alternatives like search_products or check_store_stock. No exclusions or alternatives are mentioned, only the condition 'by item number'.

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