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

With no annotations, the description carries the burden and discloses key behavioral traits: timezone (Europe/Moscow), 24-hour format, entities covered, and different outputs depending on date presence. It does not specify return structure or handling of invalid dates, but for a simple read tool it is largely transparent.

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 short and front-loads the resource and scope. The bilingual repetition adds minor redundancy but supports localization; every sentence contributes useful 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 single-parameter read-only tool with no output schema and no annotations, the description provides sufficient context: what is returned, timezone, format, and date-dependent behavior. Minor gaps like invalid date handling are not critical for correct invocation.

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 the baseline is 3. The description adds meaning beyond the schema by clarifying that without a date the tool returns today's hours, whether it is currently open, and the whole week—schema only mentions today and the week, not open-now status.

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 a specific resource (opening hours) and scope (hall, kitchen, bar) with timezone and format. It clearly distinguishes this from sibling tools like get_menu or get_restaurant_info, which cover different restaurant data.

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?

It explains behavior with and without the optional date parameter (specific day vs today/open-now/week), giving clear usage context. There is no sibling that duplicates this function, so no explicit alternative routing is needed, though no when-not-to-use guidance is provided.

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