Календарь доставки

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

No annotations exist, so the description carries full responsibility. It discloses the return format (today, tomorrow, plus 7 days with weekdays) and the critical dependency on this call for any date substitution. It doesn't mention timezone or edge cases, but the output schema covers exact structure, so this is sufficient.

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?

Four sentences that each serve a distinct purpose: what it does, when to call, why it's necessary, and how to use the result. The core function is front-loaded and there is no redundant text.

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 parameterless tool with an output schema, the description fully covers the tool's role, usage, and output integration. It leaves no ambiguity about why and how to invoke it, making it complete in context.

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 tool has zero parameters, making schema coverage trivially 100%. Per the baseline for 0 params, a score of 4 is appropriate; no parameter explanation is needed.

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 returns today's and tomorrow's dates plus the next 7 days with weekdays. This specific verb+resource distinctly separates it from sibling search/cart tools.

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 instructs to call before searching whenever the user specifies a date verbally, provides concrete examples ('tomorrow', 'by Friday'), and states the tool is mandatory because the agent has no clock. It also directs how to pass the result to search_products*.

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