Скоро испортится

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

No annotations are provided, so the description carries the full burden. It explicitly discloses that already expired items are included, which is a key behavioral detail. As a list operation, it implies read-only behavior, but no further nuances (e.g., sorting, pagination) are described.

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, concise sentence that directly conveys the tool's purpose and key behavioral note. No filler words or redundant 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 simple list tool with one optional parameter and no output schema, the description is largely complete. It states the scope and the inclusion of expired items. However, it does not describe return value structure or any limits, which might be useful but not critical for this simple use case.

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 single parameter 'withinDays' is fully described in the input schema (100% coverage), setting a baseline of 3. The description does not add extra meaning beyond the schema, but it also does not need to since the schema is sufficient.

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 clearly states it lists products expiring soon, including already expired ones. The verb 'list' and the resource 'products' with a specific criterion make the purpose unambiguous and distinguish it from siblings like 'list_fridge' which lists all items.

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 intended use is implied by the description—use it to see which products are expiring soon—but it does not explicitly mention alternatives or exclusion criteria. Sibling tools exist (e.g., 'list_fridge'), but no guidance is provided on when to choose this over them.

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