Akakçe deals (son indirimler)

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

With no annotations, the description carries the full burden; it usefully discloses that no login/auth is required and clarifies the semantic of 'deal'. However it says nothing about ordering, how many deals are returned, whether results are paginated, or freshness window – meaningful gaps for a feed tool with no output schema.

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, front-loaded with the resource definition and followed by the auth note. No filler; every clause conveys information.

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 no-param feed with no output schema, the description covers purpose and auth, but omits result volume, ordering, and recency semantics – details an agent would need to decide whether this tool alone answers a 'what's on sale' query.

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 tool takes zero parameters and the description doesn't need to explain any; the baseline for a 0-param tool is 4. Nothing in the text misrepresents the parameter-free nature.

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?

Specific verb 'döndürür' plus a precisely defined resource: 'son yakalanan indirimler (fiyatı yeni düşen ürünler)' – it even parenthetically defines what counts as a deal, which disambiguates from search or category_browse. It never names a sibling tool explicitly, so it stops short of full differentiation.

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?

The phrase 'son yakalanan indirimler' implies a browse-latest-deals use case, and the no-login note removes a prerequisite. But it gives no explicit when-to-use vs akakce_home_feed, akakce_search, or akakce_category_browse guidance and no exclusions.

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