List available delivery slots

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

With no annotations provided, the description bears the full burden. It discloses that the tool returns slots for the account's first saved address, implying read-only behavior. However, it does not disclose potential edge cases (e.g., no address saved) or authentication requirements. The description is adequate but not extra 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 two efficient sentences. The first sentence delivers the core purpose and output fields. The second sentence adds essential prerequisite context. No extraneous words.

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?

Given the tool's simplicity (no parameters, no output schema), the description is sufficiently complete. It specifies what is returned (fields) and the scope (first saved address). Minor details like error handling or default behavior could be added but are not critical.

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, and schema description coverage is 100%. The description does not need to add parameter information. According to guidelines, baseline for 0 parameters is 4, and the description meets this without deficiencies.

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 that it returns bookable future delivery slots with specific fields (id, start, end, order-until deadline, zone) and specifies the context (first saved address). However, it does not explicitly differentiate from sibling tools like set_delivery_slot, which is a closely related tool.

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 context by noting that a slot must be set before the cart can hold products, which is a prerequisite hint. However, it does not provide explicit when-to-use guidance, alternative tools, or exclusions. The connection to the sibling tool set_delivery_slot is implied but not stated.

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