List Menu Items

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it supports free-text search and active/inactive filter, and lists the returned fields. No contradictions, and the description supplements the annotations with specific capabilities.

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?

The description is two sentences in English and two in Spanish, front-loading the action 'List the kitchen menu catalog'. Every word contributes meaning; no redundancy or fluff.

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?

Given annotations cover safety, output schema documents return values, and parameters are fully described, the description provides all necessary information for an agent to select and invoke the tool correctly. It covers purpose, supported features, and output fields.

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% with bilingual parameter descriptions. The description summarizes the key parameters (q, isActive) and lists return fields, which adds information beyond the schema for parameter context (though schema already explains each parameter clearly).

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?

The description clearly states it lists the kitchen menu catalog, using the verb 'list' consistent with the tool name. It distinguishes from sibling tools like list_products by specifying it's the kitchen menu catalog and indicating the returned fields (item id, name, description, price, category, active status).

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 implies usage for browsing menu items with search/filter but does not explicitly state when to use it over alternatives like list_products or list_kitchen_tickets. No when-not-to-use or comparative guidance is provided.

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