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 shape of the returned data (categories and products with calories, cost, image), but says nothing about pagination, size, or whether the response is cached/static, which would be useful for a full-menu fetch.

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?

One front-loaded sentence that enumerates the payload fields with no filler. It is efficient, though a short usage clause would have cost little and added value.

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-value documentation is not required, and the annotations cover the safety profile. The only meaningful gap is the absence of guidance on acquiring the restaurant_id or when to prefer this over jimmy_johns_modifiers, which is partly mitigated by the parameter description.

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% and the single parameter is fully documented in the schema, including where to get the Olo restaurant id. The description adds no syntax or format detail beyond what the schema provides, 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?

The description names a specific resource (Jimmy John's restaurant menu) and enumerates its contents (categories, products, description, calories, base cost, image), so the agent knows exactly what is retrieved. It does not explicitly differentiate itself from siblings like jimmy_johns_modifiers or jimmy_johns_store, but the resource is unambiguous.

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?

There is no when-to-use guidance, no mention of prerequisites or alternatives. The schema note about obtaining restaurant_id from /jimmy-johns/nearby carries the only routing hint, and it lives in the parameter description rather than the tool description.

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