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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, and the description adds the material context an agent cannot get from annotations: the $0.002 USDC cost per call, the x402 payment rails (Base, Solana, Arc), and the fact that failed calls are not charged. Pagination behavior (36 per page plus total result count) is also disclosed. It stops short of describing rate limits or latency.

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 front-loads the resource and return fields, then covers sorting and pricing in two short follow-on sentences with no filler. The field enumeration is dense but every element is decision-relevant; a slight trim of the return-field list (already in the output schema) would tighten it further.

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?

For a read-only, single-query search tool with one required parameter and full schema coverage, the description covers scope, cost, billing failure semantics, page sizing, and sort options. An output schema exists, so the enumerated return fields are redundant but harmless; nothing needed to invoke the tool correctly is missing.

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 100%, so the baseline is 3. The description earns the extra point by supplying '36 per page plus the total number of results', which is the only place an agent learns how to interpret the page parameter, and by restating the sort dimensions in human terms rather than just enum-like tokens.

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 verb and resource ('Hepsiburada (Turkey) product search') and enumerates the exact fields returned, which makes it impossible to confuse with a general search or with another marketplace sibling such as ecommerce_trendyol_turkey. The platform and country scope act as the differentiator even without naming a sibling explicitly.

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 implied by the platform scoping: search this tool when you want Hepsiburada listings. However, there is no explicit statement of when to prefer it over ecommerce_trendyol_turkey or a broader retail aggregator, and no when-not guidance. The sort options are described but not tied to selection advice.

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