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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable behavioral context: it accesses a public JSON feed, requires no authentication or proxies, and costs $0.02/call with USDC on Base. This goes beyond the annotations and gives the agent a clear picture of network and billing implications.

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 two concise sentences. The first sentence front-loads the core function and output fields, while the second adds access method and pricing. Every clause earns its place, with no redundant or filler content.

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?

The description completely explains outputs (fields returned) and access constraints (public feed, no login/proxies). Combined with thorough schema and annotations, this covers the essential usage context for a simple scraping tool. It omits edge-case behaviors like rate limiting or error handling, but these are not critical given the tool's simplicity and annotation coverage.

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?

The input schema provides 100% coverage of both parameters (items and maxConcurrency) with detailed descriptions, including subdomain format and concurrency limits. The tool description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool pulls live product catalogs from Zid storefronts, listing specific fields (name, price, sale price, category, image). It distinguishes itself from siblings by explicitly targeting Zid, a Saudi/Gulf e-commerce platform, while sibling tools focus on Shopify or general web scraping.

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 implies when to use the tool: for pulling product data from Zid stores via public JSON feed without login, browser, or proxies. It also mentions per-call cost, which is useful context. However, it does not explicitly state when not to use it or name alternative tools, though sibling names provide implicit guidance.

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