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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds useful context by enumerating the per-restaurant signals returned (open state per channel, delivers-to-you, blackout/overloaded flags, ETAs, fees), but says nothing about auth requirements, rate limits, or failure modes for unavailable ids.

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; the purpose and return contents are stated immediately. The field enumeration is dense but each item is informative rather than padding.

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 the description need not explain return values, and all three required params are documented. The batch scope and availability-relative-to-diner-location framing make it complete enough for correct invocation, though no usage routing to siblings is provided.

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 100%, so the schema already documents latitude, longitude, and the comma-separated restaurant_ids with the 'up to 20' cap. The description restates the batch/20 limit but adds no new parameter meaning, so the baseline 3 applies.

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 verb+resource ('Grubhub batch ordering availability') and enumerates the returned fields, which makes the tool's scope clear against siblings like grubhub_search, grubhub_restaurant_menu, and grubhub_timepicker. It does not explicitly name those siblings, so it stops short of full differentiation.

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 only implied: 'batch' plus 'up to 20 restaurants' signals this is for checking availability of already-known restaurant ids rather than discovery. There is no explicit when-to-use, when-not, or pointer to alternatives such as grubhub_search for discovery or grubhub_timepicker for ordering slots.

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