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

With no annotations and no output schema, the description carries the full behavioral burden. It partially compensates by disclosing the credit cost ('flat 5 points per successful run') and enumerating returned fields, but says nothing about pagination, result limits, auth requirements, or failure modes. Useful additions, yet incomplete for an unannotated 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, zero filler, front-loaded verb and resource. The field enumeration and cost note both earn their place since no output schema or annotations exist to convey them.

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 simple one-parameter lookup with no output schema, listing the returned attributes (seller id, name, price, list price, rating, city, shipping flags, buybox winner) gives the agent a solid picture of the response, and cost is disclosed. Pagination and limits remain unaddressed, which is the main remaining gap.

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% and the single 'product' parameter is documented as 'SKU, product group ID or URL. e.g. HBCV00004X9ZCK', including an example. The description adds no format or identifier semantics beyond what the schema already provides, so baseline 3 applies.

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 ('List all sellers (merchants) offering a Hepsiburada product') and enumerates the concrete return fields, so the inverse relationship to run_hepsiburada_merchants_products is implicit. It never names a sibling explicitly, so it stops short of full differentiation, but the purpose is unambiguous.

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: given a product SKU/URL, retrieve its competing sellers. There is no explicit when-to-use, no 'use X instead' routing to run_hepsiburada_merchants or run_hepsiburada_products, and no prerequisites stated. Adequate but leaves the agent to infer the call context.

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