Akakçe search filters

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

No annotations are provided, so the description carries the full disclosure burden. It does describe the return payload (filter groups and their ids) and the downstream chaining behavior, but says nothing about authentication, whether results are cached or live, or any rate limits.

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 tight sentences: the first declares what is returned, the second declares how to use the result. Nothing is wasted and the key information is front-loaded.

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 two-parameter read tool with no output schema, the description adequately conveys the output's shape and purpose. However, the undocumented sort parameter and the absence of any hint about result size or filter availability mean the definition is only minimally sufficient.

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 only 50%. The phrase parameter's schema text ('Arama ifadesi') merely restates the name, and the description repeats 'arama ifadesi' without adding format or example guidance. The sort parameter (default 1) is unexplained in both the schema and the description, leaving its accepted values opaque.

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 names a specific verb and resource: it returns the applicable filter groups (brand, feature, RAM, etc.) and each filter's id for a given search phrase. That is concrete and distinguishable from siblings such as akakce_product_detail or akakce_deals, though it never contrasts itself directly with akakce_autocomplete or akakce_category_browse.

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?

It states the intended workflow explicitly: call this to obtain filter ids, then pass those ids to akakce_search as filterIds to narrow results, which effectively names the alternative and the condition for chaining. It stops short of stating when not to use it, such as when no filtering is needed.

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