Akakçe quickview (tek ürün)

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 add valuable auth context ('Giriş gerektirmez') — relevant given the akakce_login sibling — but says nothing about return shape (what fields describe a 'cheapest seller'), behavior for an invalid/unknown code, or whether results are cached/rate-limited.

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 short sentences with zero padding: the operation and scope come first, the sibling comparison and auth note follow. Every clause earns its place.

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 one required param and no output schema, the description needs to carry return-value expectations; it only says 'cheapest seller(s)', leaving the response structure (price, seller name, currency, ranking) unspecified. The auth note helps, but for a network-backed lookup tool the behavioral picture is still thin.

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% and the single parameter is already documented as 'Ürün kodu'. The description only echoes that ('tek bir ürün kodu için') and adds no format, range, or sourcing detail beyond the schema, so the 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 and resource ('en ucuz satıcı(ları) hızlıca döndürür') scoped to a single product code, and explicitly names the sibling it is a reduced form of (akakce_product_prices). An agent can distinguish it from the other 19 akakce tools without opening a schema.

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?

Names the alternative (akakce_product_prices) and characterizes this one as its 'tekli/hafif sürümü', which signals the single-product, lightweight use case. It stops short of an explicit rule for when to prefer the fuller sibling (e.g. batch codes or extra fields), so the choice is implied rather than fully prescribed.

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