Что в холодильнике

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

With no annotations, the description carries the burden of behavioral disclosure. It explains what will be shown (all contents with specific fields), but does not disclose additional behaviors such as whether expired items are included (though 'всё' implies yes), ordering, or potential edge cases like an empty fridge. Still, for a simple read-only list, the provided info is acceptable.

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 that clearly states the tool's function and return contents. Every word earns its place, with no redundant information or fluff.

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 no params and no output schema, the description adequately explains what is returned. It lacks details about sorting, formatting, or whether expired items are included, but 'всё содержимое' covers inclusiveness. The description is complete enough for an agent to understand the tool's basic function and output expectations.

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?

There are zero parameters, so the description needs no parameter explanation. The baseline for 0 params is 4, and the description adds value by describing the returned data fields (products, quantity, location, expiration date), which fully compensates for the lack of output schema.

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 the tool shows all fridge contents including products, quantity, location, and expiration date. The verb 'показывает' (shows) is specific, and the resource 'холодильник' (fridge) with the listed attributes distinguishes it from sibling tools like check_fridge_item or expiring_soon.

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 implies usage for viewing an overview of everything in the fridge, but it does not explicitly mention when to use this tool versus the siblings (e.g., check_fridge_item for a specific item, expiring_soon for soon-expiring items). No exclusions or alternative recommendations are provided.

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