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 genuine extra context beyond the annotations: it discloses that only 'published' items appear and that the response contains no prices or nutrition values, which sets accurate expectations about result contents.

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 tight sentences, front-loaded with the resource and scope, followed by the exclusion note. Every clause carries information with no filler.

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 a rich output schema, parameter documentation is not required in the description, and all seven params are schema-documented. The description covers scope, filters, and data exclusions, leaving only minor detail (pagination specifics) unstated, which the 'one page' phrasing partially signals.

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%, so all seven parameters are self-documented in the schema. The description echoes that free-text and the four taxonomies are the filter dimensions but adds no format or syntax detail beyond the schema. 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?

States a specific verb+resource: a catalog returning 'one page of published menu items' for Chick-fil-A. The phrase 'one page' implicitly distinguishes it from a detail tool like chick_fil_a_menu_item, though it does not name that sibling 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 explains how to filter (free text plus the four taxonomies), which implies usage, but never states when to pick this tool over chick_fil_a_menu_item or chick_fil_a_menu_taxonomy. No explicit alternatives or when-not conditions are given.

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