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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds provenance (ministry-published, i.e. authoritative official data) and a scope boundary, which is genuinely useful context. It says nothing about result volume, pagination behavior via cursor/page_size, or freshness of price data.

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?

It is short and front-loads the data source, with zero padding. But the second sentence is telegraphic to the point of ambiguity — 'category: bread or chain_id/product_id' reads as a syntax fragment rather than a clear statement of allowed filter combinations.

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?

An output schema exists, so return values need no explanation. For a 7-parameter, enum-heavy, paginated tool with 0% schema description coverage, however, the description leaves search, sorting, and paging semantics entirely unexplained and misrepresents the category enum as a single value.

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 0% across 7 parameters, so the description must compensate and it covers only category, chain_id and product_id. It omits q, sort, cursor and page_size entirely, leaving pagination and free-text search undocumented. Worse, it says 'category: bread' while the enum contains eight categories, which understates the actual capability.

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?

It names the resource and publisher ('MOET-published Dubai shop prices'), which is more specific than a restated name. But it never distinguishes itself from close siblings like grocery_products or shopper_price_reports, so an agent cannot tell from the description alone which of these price sources to call. 'Not online offers' is a scope hint, not a differentiation statement.

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 fragment 'category: bread or chain_id/product_id' implies mutually exclusive filtering modes, and 'Not online offers' functions as an exclusion. However, no alternative tool is named for when the agent actually wants online/retail prices or comparative grocery data, so the routing decision is left to inference.

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