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

With readOnlyHint=true already declaring safety, the description adds genuinely new behavioral context: matching covers both names and descriptions, both English and Hebrew are matched, and an empty query returns the full list. It does not disclose pagination/cursor behavior or result ordering, which would matter for a listing tool.

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?

Three short sentences, each earning its place: purpose first, matching/language semantics second, currency units third. Nothing is repeated from the schema and nothing is padding.

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?

No output schema exists, and the description never characterizes the return shape or how pagination cursors work, which an agent needs for a listing tool with nested filters and pagination. The nested-object complexity is only partially addressed.

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?

At 50% schema coverage, the description compensates for the most consequential gap: prices are integer agorot (ILS minor units), which the bare integer min/max schema does not say. It also clarifies query matching semantics. However, filters.categories, pagination.limit/cursor, and the intent field are left entirely to the schema, so coverage is only partial.

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?

States a specific verb and resource ('Search the shop's herbal remedies and natural cosmetics'), which scopes the catalog to a concrete domain. It does not, however, distinguish itself from the sibling lookup_catalog or get_product, so an agent cannot tell from this text alone which of the two catalog tools to pick.

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?

'An empty query lists everything' implies a browse mode and hints at when to use it with no terms. There is no explicit guidance on when to prefer this over lookup_catalog, get_product, or when to apply filters, so selection between siblings remains inferred.

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