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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: output is priced and stocked per the specific cafe, includes full nutrient and allergen data, and reflects live catering stock status.

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 tightly packed sentences that front-load the resource and its cafe-specific nature before the ordering-context caveat. No filler, though the second sentence is more contextual flavor than operational instruction.

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, return-value detail is not required, and the description adequately conveys scope (one cafe, catering, live data). It could be more complete by naming the sibling retail menu tool explicitly, but nothing an agent needs to call it 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 description coverage is 100% and the single cafe_id param is fully documented in the schema. The description reinforces that pricing, availability, and nutrition are cafe-specific, but adds no syntax beyond what the schema already provides, so 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?

Names a specific resource (catering category list and item catalog for one cafe) and details what it returns (prices, nutrient panel, allergens, stock status). The closing note that catering is a 'separate application from its retail site' conceptually distinguishes it from the retail menu siblings, though it never names the sibling tool.

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: the remark that catering differs from the retail site hints an agent should pick this over a retail menu tool when ordering catering, but there is no explicit when-to-use, when-not, or named alternative. No prerequisites or scoping conditions are stated.

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