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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the content list but no behavioral depth (auth, freshness, rate limits). With annotations carrying the safety load and an output schema present, a 3 is appropriate.

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 zero filler; the resource name leads and the payload enumeration follows immediately.

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?

For a one-param read tool with a full output schema and annotations covering safety, the description is sufficient. The only minor gap is the absence of sibling routing, which is not strictly required for correct invocation.

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% and the single restaurant_id param is fully documented in the schema (numeric id from /grubhub/search). The description adds no formatting or sourcing detail beyond what the schema already supplies, so the baseline of 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 clear verb+resource ('Grubhub restaurant detail') and enumerates the returned fields (address, coordinates, rating, tags, service hours). An agent can tell this is a detail-lookup tool distinct from the menu/reviews siblings, though no sibling is named explicitly.

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: it's a detail lookup that needs a restaurant_id, so an agent infers it follows grubhub_search. There is no explicit 'use this when...' guidance, no exclusions, and no routing to grubhub_restaurant_menu or grubhub_restaurant_reviews.

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