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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds real value beyond that by disclosing the response shape (category names plus counts), the optionGroups structure for items with choices, the selectedOptions convention for ordering, and pagination behavior. It stops short of error handling or limits, so not a 5.

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?

Three dense sentences with the purpose front-loaded and zero filler; the optionGroups sentence is information-heavy but each clause carries usable guidance. Slightly compressed, but nothing should be cut.

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 no output schema, the description carries the burden of describing returns and does so (category names and counts, optionGroups, selectedOptions), plus a recommended call sequence and pagination guidance. For a read-only listing tool whose safety profile is covered by annotations, this is complete enough to invoke correctly.

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 only 40% (limit, offset, and restaurantId are undocumented in the schema), so the description must compensate. It explains the filtering role of category and query and says to paginate with limit and offset, but never states defaults (30/0), the 100-item cap, or what offset actually indexes into, leaving the numeric params partially opaque.

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 (List) and resource (a restaurant's menu items), which is unambiguous against siblings like list_room_types, list_events, or list_saved_locations. An agent can tell what this returns without opening the 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?

Gives an explicit two-step workflow: call with only restaurantId to see category names and counts, then narrow with category and/or query 'rather than reading the whole menu'. It also names the condition under which optionGroups/selectedOptions matter (items with choices) and the required=true constraint.

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