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 without description help. The description adds the per-item/per-cafe scoping context, but says nothing about return format, freshness, or pagination; with an output schema present the missing return details are acceptable, so a baseline 3 fits.

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, and the parenthetical examples earn their place by clarifying what an upsell suggestion looks like. Slightly terse in omitting an explicit verb, but not wasteful.

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, full annotation coverage, and one fully documented required parameter, the description needn't explain return values. It supplies enough context (cafe-scoped, per-item add-ons) for correct invocation; only the when-to-use routing is absent.

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 single parameter is fully documented in the schema ('Required. Panera cafe id, from /panera/locations.'), and the description never mentions cafe_id. With 100% schema coverage, the schema carries this dimension and the baseline 3 is appropriate.

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 ('per-item upsell/add-on suggestions') and scopes it to 'One Panera Bread cafe,' with concrete examples (Extra Turkey, Extra Bacon for a Bacon Turkey Bravo) that make the concept unambiguous. It contrasts implicitly with sibling tools like panera_item_options and panera_menu, though it never explicitly names an alternative verb or route.

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 statement of when to use this tool versus alternatives such as panera_item_options or panera_item_detail, and no prerequisites beyond the cafe scoping. Usage is only inferable from the subject matter.

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