Akakçe category browse

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool returns products and quickFilters and that filterIds narrows results, but it is silent on pagination despite a page parameter, on authentication needs, and on the shape or limits of returned product lists.

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 short sentences, front-loaded with the core action and return values, then usage guidance. Every sentence contributes either purpose, narrowing behavior, or ctCode acquisition.

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 browse tool with three parameters and no output schema, the description covers purpose, return content, and ctCode sourcing. However, it omits pagination behavior for the page parameter and does not describe the structure of the returned products or quickFilters, leaving real gaps for an agent invoking it.

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?

The schema already describes ctCode and filterIds at 67% coverage, so the baseline is moderated. The description adds useful provenance for ctCode and restates that filterIds narrows the query, but it never mentions the page parameter, leaving that part of the schema and description both uninformative.

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: browsing a category code (ctCode) to return products and quickFilters. It distinguishes itself from sibling akakce_search_filters by explaining that this tool consumes ctCode, and from keyword-search siblings by explaining where a ctCode can be obtained.

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 gives clear context for when to use the tool: after obtaining a ctCode from search results, product URLs, or akakce_search_filters. It also explains that filterIds narrow the browsing result. It does not explicitly state when to prefer akakce_search instead, so it falls short of a full alternatives matrix.

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