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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds that results span multiple shops and names the returned fields, but says nothing about result volume, whether limit caps the response, or what happens when a catalog matches nothing — a meaningful gap 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?

Two sentences, front-loaded with what the tool returns before the input formats. Dense and mostly waste-free, though the second sentence duplicates schema text that an agent would read anyway.

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?

With no output schema, the description usefully enumerates returned fields, which is the right compensation. However, it omits any mention of the 50-item limit cap, default sorting, or empty-result behavior, leaving the agent without a sense of result size or ordering by default.

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 60% and the schema already documents catalog, locale (including currency mapping), and max_price. The description's catalog guidance largely restates the schema's 'Catalog URL, platform/category or platform slug' with a concrete URL example, which helps slightly, but sort and limit receive no explanation anywhere.

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 resource (offers of one platform/category from the accounts catalog, across shops) and enumerates what each offer carries: price, stock, seller shop, product page, buy link. That is concrete and distinguishable in substance from search_accounts, though the sibling is never named, so differentiation relies on the agent inferring it.

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 gives useful input-form guidance (URL, 'platform/category' slugs, or a platform slug), which tells the agent HOW to call it but not WHEN to choose it over search_accounts or compare_hosts. No exclusions or alternative-routing guidance is present, so usage is implied rather than stated.

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