CommerceAI

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

With no annotations, the description carries behavioral disclosure and covers key traits: US-only catalog scope, thread continuation via conversation_id, selected product references via item_id, and an explicit warning not to parse those values. Gaps remain around read-only/side-effect status, credit implications, and rejection behavior, which are only present in schema descriptions.

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 short and front-loaded: purpose first, then key parameter usage, then exclusions. Every sentence contributes to selecting or invoking the tool, with no redundant or filler content.

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?

For a 5-parameter tool with full schema coverage and no annotations, the description provides enough to select and invoke it correctly, including domain exclusions and ID handling. It does not describe return values or response structure, though the lack of an output schema makes that a modest remaining gap.

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 the baseline is 3. The description adds practical framing for query, conversation_id, and selected_item_ids, but most of this meaning is already present in the schema descriptions, and it does not mention locale or market parameters.

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 opens with a specific verb set and resource: find, compare, or answer questions about products in the US catalog. It also scopes out unrelated domains such as cart, orders, coupons, account login, and non-US markets, so an agent can distinguish its purpose without any sibling tools.

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?

It explicitly says when to use the tool for product search/comparison/questions and when not to use it, naming cart, orders, coupons, account login, and non-US markets. It also explains continuation and product-reference cases, leaving little ambiguity about invocation conditions.

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