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 real value beyond that by describing the returned structure (category and product records) and the fields included. It does not mention pagination, rate limits, or whether the full menu is returned in one call.

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 sentences with no filler. The payload description is front-loaded and the routing/provenance guidance follows compactly; every clause earns its place.

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 an output schema present and annotations covering the safety profile, the description supplies everything needed to call correctly: the single required parameter's provenance and the surrounding workflow siblings. Nothing material is missing.

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 schema already documents restaurant_id as an Olo id from /jimmy-johns/nearby. The description's note that restaurant_id comes from jimmy_johns_nearby largely repeats the schema, so baseline 3 applies with only marginal added meaning.

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 (Fetch) and resource (one Jimmy John's restaurant menu), scoped as category and product records, and enumerates the payload (descriptions, calories, base cost, images). This distinguishes it cleanly from jimmy_johns_modifiers and jimmy_johns_store.

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?

Explicitly states where restaurant_id comes from (jimmy_johns_nearby) and routes to the right siblings for adjacent needs: jimmy_johns_modifiers for customization choices and jimmy_johns_store for store details. When-to-use vs alternatives is fully specified.

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