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

Annotations already provide readOnlyHint and openWorldHint, and the description does not contradict them. It adds useful behavioral detail by specifying the 50-item limit and the returned compact fields (name, price ex/inc VAT, stock, link). It does not cover not-found behavior, but the safety profile is already handled by annotations.

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 short, front-loaded sentences with no filler. It states the action, constraints, and return fields efficiently, and every sentence adds value.

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 simple read-only batch lookup with no output schema, the description covers the essential lookup keys, the maximum batch size, and the main returned fields. It omits edge-case behavior such as invalid or missing identifiers, but these are minor for safe invocation.

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 only 33%, and the description partially compensates by explaining the two lookup keys (SKU or numeric id) and the batch size. However, it does not clarify whether at least one of ids/skus is required or whether both can be used together, which is a meaningful gap given that required parameters is 0.

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 uses a specific verb and resource: 'Look up up to 50 products at once by SKU or by numeric id.' It clearly identifies the batch-lookup scope and distinguishes it from single-product get_product or search-oriented siblings like search_products and list_products.

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 context is clear: this tool is for retrieving multiple known products by SKU or numeric id, not for searching or listing. It does not explicitly name alternatives or exclusions, but the identifier-based lookup context leaves little ambiguity about when it applies.

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