Akakçe product search

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

No annotations exist, so the description carries the full burden. It does usefully disclose the exact return fields (name, brand, lowest price, seller count, rating, product code, URL) and that the product code feeds price/detail calls. It says nothing about pagination limits, auth requirements, or rate limiting, leaving meaningful behavioral gaps.

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?

Three dense sentences with no filler: purpose first, return fields second, pagination/filtering last. Well front-loaded, though the return-field enumeration is long enough that it slightly crowds the actionable guidance.

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 no output schema, the description correctly compensates by enumerating the returned fields, and it covers the key filtering/pagination mechanics for a 5-parameter search tool. Minor gaps remain around result limits and cross-tool routing, but nothing an agent needs to call it 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 schema already defines all five parameters and the baseline would be 3. The description adds value beyond the schema by explaining that filterIds should be sourced from akakce_search_filters and that ctCode+filterIds combine for filtering, giving an agent the provenance it needs.

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 ('Akakçe'de ürün arar') plus the return shape (price list), making the core action unambiguous. It does not explicitly differentiate itself from search-adjacent siblings like akakce_deals or akakce_autocomplete, so it stops short of a 5.

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?

Gives clear operating context: pagination via 'page', filtering via 'ctCode + filterIds', and explicitly routes the agent to akakce_search_filters to obtain filter ids. It never states when NOT to use this versus sibling search/browse tools, so no exclusions are provided.

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