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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by explaining the method ('via their own public JSON feed'), explicitly stating no login/browser/proxies, and disclosing the cost per call ($0.02/call). This goes beyond the safety profile provided 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?

A single, information-dense sentence followed by a brief cost/access note. Every element serves a purpose: what it does, data fields, platform context, auth requirements, and pricing. No wasted words.

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?

Despite no output schema, the description lists the return fields (name, price, sale price, category, image), enough for an agent to interpret results. It explains the data source (public JSON feed) and operational constraints (max 20 shops, concurrency). With strong annotations and full schema coverage, the description is complete for effective selection and 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 100%, with both items and maxConcurrency parameters well documented in the schema. The description does not add parameter details beyond the schema, so it meets the baseline for high schema coverage. The schema itself is informative about subdomain formats and concurrency limits.

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 ('Pull live product catalogs') with a clear resource ('Zid storefronts'), explicitly listing the data fields (name, price, sale price, category, image). It clearly distinguishes this tool from siblings by targeting Zid specifically, whereas sibling tools focus on Shopify or generic e-commerce.

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 description provides clear context for when to use this tool: when needing product data from Zid storefronts, noting it's a common Saudi/Gulf e-commerce SaaS. It also implies no authentication is needed ('No login, no browser, no proxies'). However, it does not explicitly mention alternatives or exclusions, such as 'use Shopify tools for Shopify stores'.

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