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

With no annotations, the description adds key behavioral context: the time window (last 90 days) and the 'deliverable' constraint. However, it omits aspects like sorting order (presumably by sales) or pagination behavior, which would be helpful for an agent.

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 a single sentence that efficiently conveys purpose, scope, and use case with no wasted words. It is front-loaded and easy to parse.

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?

Given the tool's simplicity (no nested objects, no output schema), the description covers purpose, scope, and intended use. It lacks details on return format or pagination, but for a list tool with only two parameters, it is adequately complete.

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%, so baseline is 3. The description does not add semantic value beyond what the schema provides for 'limit' and 'kategorie_id'; it only confirms their optionality.

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 the tool lists best-selling deliverable items from the last 90 days, optionally per category. It clearly distinguishes from siblings like search_products or get_recommendations by specifying the scope (recent top sellers) and use case (recommendations and initial queries).

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 description explicitly says 'Good for recommendations and initial questions,' providing clear context for when to use the tool. However, it does not mention when not to use it or point to alternatives among siblings, such as search_products for specific queries.

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