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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds real value beyond them by disclosing the date default behavior and the shape of the result (next dates, preparation time, upcoming closed days), which is exactly the context an agent needs for a read-only query.

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 dense but well-formed sentence that front-loads the core purpose and appends the default behavior and return contents. Nothing is wasted, though the parenthetical default slightly interrupts the flow.

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?

There is no output schema, so the description carries the burden of describing returns, and it does: available times, next dates, preparation time, and closed days. Combined with full schema coverage and rich annotations, an agent has enough to call the tool correctly.

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, but the description adds meaning the schema lacks: the date parameter's default (the first date with times), which the schema only labels 'YYYY-MM-DD'. It also implies the shop/fulfillment pairing through context. Above baseline.

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?

States a specific resource (available pickup/delivery times for a shop on a date) with additional scope (next dates, preparation time, closed days). An agent can tell this is an availability-lookup tool, distinct from order_status or quote_order, though it never names a sibling to sharpen the distinction.

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?

Usage is implied — check availability before placing an order — but there is no explicit when-to-use, when-not, or mention of an alternative tool. The 'default: the first date with times' tells the agent the date param is optional without stating when to omit it.

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