Akakçe product prices

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 discloses the returned fields and bulk behavior, but does not mention authentication needs, rate limits, error behavior, or whether it is strictly read-only.

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?

The description is short and front-loaded: it states the purpose first, then the returned fields, then sourcing and bulk guidance. Every sentence adds useful information without waste.

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 single-parameter tool with no output schema, the description is largely complete: it explains the purpose, return fields, and where to obtain valid codes. The main remaining gaps are error behavior and operational constraints, which are minor given the tool's simplicity.

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 already 100%, so the baseline would be 3. The description adds meaning beyond the schema by explaining that codes should come from search or autocomplete results and that multiple codes can be supplied in one bulk call.

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 action and resource: it returns the cheapest sellers for one or more product codes from Akakçe, along with the returned fields. It is clear but does not explicitly distinguish this tool from the similarly named sibling akakce_quickview.

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 useful sourcing guidance, telling the agent to get product codes from akakce_search or akakce_autocomplete, and encourages batching multiple codes. However, it does not say when to use this tool instead of akakce_quickview, akakce_product_detail, or akakce_price_history.

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