run_hepsiburada_merchants_products

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

No annotations exist, so the description carries the burden. 'List' implies a read operation and the '1 point per returned record' clause usefully discloses the credit cost of the call, which is real behavioral value. However, it says nothing about pagination limits, rate limits, or return shape, leaving meaningful gaps for a 16-param read 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, front-loaded with purpose and facets, then the credit cost. No filler. Slightly dense enumeration of facets, but every clause carries information.

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 16-parameter read tool with no annotations and no output schema, the description covers purpose and cost but omits return format, pagination behavior, and any indication of what filters combine well. Adequate but with clear gaps.

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 every parameter is already documented in the schema (including enum expansions and examples). The description only restates a subset of the filter facets (brand, color, price range, rating, delivery, discount, photo reviews) without adding syntax or format detail, 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+resource+scope: listing products sold by a named Hepsiburada merchant, plus the available filter and sort facets. The merchant-scoped framing implicitly distinguishes it from keyword-based siblings like run_hepsiburada_products_search, but it never names an alternative 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 merchant-scoped purpose (fetch a given store's catalog), but there is no explicit when-to-use, when-not, or routing to siblings such as run_hepsiburada_products_search or run_hepsiburada_products. The agent must infer the selection criteria.

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