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

Annotations only cover readOnly/openWorld, so the description carries the rest and does so well: it discloses the residential-proxy provenance, a per-call price of $0.01 USDC paid via x402 (Base, Solana, Arc), and critically that failed calls are not charged. It also states the 36-results-per-page granularity, which an agent needs to reason about pagination cost; only the absence of any rate-limit or latency note keeps it from a 5.

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 purpose and site are front-loaded, followed by the field inventory and then operational details. The field list is dense and partly redundant with the output schema, but every clause is concrete and none is filler.

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 an output schema present, the description need not have re-enumerated return fields, but the things an agent genuinely cannot infer – payment requirement, cost, billing on failure only, proxy sourcing, page size – are all covered. For a 2-parameter read-only search tool this is essentially complete; it lacks only guidance on sibling selection.

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%, so the schema already explains both parameters including the 1-50 page range and the 'Turkish works best' hint. The description adds only the useful fact that a page yields 36 products, which helps translate a result target into a page number; baseline 3 applies when the schema does the heavy lifting.

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 ('Trendyol (Turkey) product search') and enumerates exactly what comes back: id, name, brand, category, price in TRY, discount, rating, best-seller rank, favourites, merchant id, image and link. That field inventory makes it trivially distinguishable from sibling product search tools such as ecommerce_hepsiburada or ecommerce_aliexpress.

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?

Usage is only implied by the site name – an agent infers 'call this when you want to search trendyol.com'. There is no explicit when-to-use statement, no guidance on choosing this over the Turkish sibling ecommerce_hepsiburada, and no mention of the page cap (1-50) as a retrieval constraint in the prose.

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