search_products

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

With no annotations, the description carries the full behavioral burden and does so well: read-only, no account required, conservative pacing, explicit failure/blocked statuses, and unsupported basket/checkout actions. These details are directly relevant to safe and correct invocation.

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 front-loaded, efficient, and well structured. Each sentence adds useful information about scope, return fields, limitations, or behavior without unnecessary repetition.

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 there are no annotations and no output schema, the description sufficiently explains return fields and failure statuses. It also covers account requirements and operational limits, leaving no significant gaps for calling the tool correctly.

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 count, offset, query, and queries are already documented. The description adds useful semantic context for batch mode by explaining that queries can represent shopping-list items and are run sequentially with conservative pacing.

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 states a specific verb and resource: searching the Tesco Ireland grocery catalogue. It also clarifies single-query and batch modes, making the tool’s role unambiguous even without siblings.

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 covers when to use single-query versus batch mode, including batch size limits and shopping-list usage. It also clearly states when the tool is not appropriate by excluding basket and checkout operations.

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