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

With no annotations, the description carries the full disclosure burden. It usefully states the result ordering (deal score, discount vs market descending), but omits read-only confirmation, result-count limits, pagination, and how multiple country filters combine.

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?

A single front-loaded sentence with no filler; the ranking criterion, the most decision-relevant detail, is included inline rather than padded out.

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, zero-required-parameter read tool with no output schema, the description conveys what the results are and how they are ordered. Only minor gaps remain, such as how many deals come back and whether the country list acts as an OR filter.

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 100% and the single optional 'countries' parameter is documented with its default (CZ) and enum values. The description adds no meaning beyond that, 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?

The description names a specific resource (deals) with an explicit scope and ranking rule ('top deals right now, ranked by deal score, biggest discount vs market first'). It's clear what the tool returns, but it never distinguishes itself from the close sibling search_deals, leaving the agent to infer the boundary.

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?

'Right now' hints at a live, curated feed versus historical tools like get_price_history, but there is no explicit when-to-use or when-not-to-use guidance. The most relevant alternative, search_deals, is never named, so the agent must guess which one to call.

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