pickup_slots

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data exposure are covered. The description adds the useful notion of real-time availability ('currently available'), implying results may change between calls, but does not discuss rate limits, caching, or whether an empty result means no slots.

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 with no filler; every clause (available, pickup, dates/times/meal periods, per store) contributes to selecting and calling the tool correctly.

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?

With no output schema, the description usefully enumerates the returned shape (dates, times, meal periods), which is its main contribution. But for a tool with two required, fully undocumented parameters and an opaque 'account' argument, an agent lacks enough information to call it confidently.

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 description coverage is 0% — neither 'account' nor 'store_code' has any documented format, constraints, or meaning. The description only loosely implies a store-scoping parameter ('for a store') and says nothing at all about what 'account' identifies or how it relates to store_code, so it fails to compensate for the schema gap.

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 names a specific verb and resource — retrieving currently available pickup dates, times, and meal periods for a store — which is far more informative than the name 'pickup_slots' alone. It does not explicitly distinguish itself from siblings like store_get or menu_list, but the resource is distinct enough that confusion is unlikely.

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 word 'currently available' implies this is a live-availability lookup rather than a static store lookup, which hints at when to use it. However, there is no explicit when-to-use vs. when-not guidance and no mention of alternative tools for scheduling or ordering downstream.

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