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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one genuinely useful behavioral detail not in the annotations: taxonomy terms are resolved to human-readable names. It says nothing further about permissions, failure modes, or resolution depth, so it is adequate but not rich.

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. The lookup mechanism comes first and the taxonomy-resolution note follows, so 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?

For a read-only detail tool with a full output schema and 100% parameter coverage, the description supplies what an agent needs to select and call it: the entity, the identifier options, and one notable enrichment behavior. Adding explicit sibling routing would make it complete.

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%, so both parameters are fully documented in the schema, including the mutual-exclusion rule. The description restates 'by id or slug' but adds no format hints, slug conventions, or error behavior beyond that. Baseline 3 is appropriate when the schema does the work.

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 (retrieve detail), resource (Chick-fil-A menu item), and lookup keys (id or slug), plus a distinguishing note that taxonomy terms are resolved to names. It implicitly separates itself from chick_fil_a_menu (a list) and chick_fil_a_menu_taxonomy, though it never names those siblings explicitly.

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?

The description gives no when-to-use vs when-not-to-use guidance and no mention of the alternative tools (chick_fil_a_menu, chick_fil_a_menu_taxonomy). The only usage constraint, 'either id or slug, not both,' lives in the schema rather than the description, leaving routing entirely to inference.

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