delivery_info

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

With no annotations, the description carries the full behavioral burden, and it discloses only the auth requirement. It does not state that this is a read-only lookup, what the response contains, or whether cut-off times vary by address/fulfilment context — meaningful gaps for a logistics-information tool.

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?

Two short, front-loaded sentences with no filler — the resource is stated first and the auth prerequisite second. It is efficient, though it errs toward under-specification rather than verbosity.

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?

An output schema exists, so return values need not be described, and a zero-parameter tool is low complexity. Still, the description omits how this differs from the several delivery/fulfilment siblings, leaving an agent to guess which one to call.

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 takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. The schema is empty and fully self-explanatory.

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?

"Delivery information and cut-off times" names the resource and adds one concrete content hint (cut-off times), but the operative verb is left implicit and "information" is close to restating the tool name. It gives no signal distinguishing it from siblings like my_delivery_slots, fulfilment_selection, or checkout_timeslots, which plausibly overlap.

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?

"Requires login" is a prerequisite, not usage guidance. There is no statement of when to call this versus my_delivery_slots or checkout_timeslots, and no exclusions or conditions are offered.

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