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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's job is to add what they can't say. It does that with "does not run recognition again," which tells the agent this call is cheap and will not re-trigger pipeline work, and it discloses that the response includes a private open-in-ChefBear link. It stops short of describing what happens when a menuId is invalid or belongs to another account, so it is strong rather than complete.

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?

Front-loaded with the use condition, then the read behavior, then the exclusions — a sensible order with no filler sentences. The middle clause listing use cases ("what to order, what a dish on it is, prices, or dishes that fit their tastes, budget or group") is slightly long but ties directly to the invocation trigger rather than padding.

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 single-parameter, fully-described, annotated, read-only tool with an output schema, the agent needs only when-to-use, what-is-returned and where-else-to-look. All three are present, and the description even explains return contents despite an output schema existing, which is a bonus rather than a gap.

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 menuId parameter's schema description already states both accepted forms (the id from list_menus/get_import_status, or the my-menu URL). The description restates the same two forms rather than adding syntax, validation, or edge-case meaning. This is the baseline case where the schema carries the parameter semantics.

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 and resource ("Reads the menu by its menuId or its ... link") and enumerates exactly what comes back: dish names, short descriptions, categories, prices, and a private link. It also names the two sibling tools it is not (list_menus, get_shared_menu), so an agent can distinguish it without opening any schema.

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?

Opens with an explicit use condition ("Use this when the user wants help with one of their saved ChefBear menus") and follows with the exclusion: "Does not search menus: use list_menus to find a menuId, and get_shared_menu for a https://chef-bear.com/m/ share link." Both the when and the when-not are stated with the correct alternative named.

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