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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: currency is USD, the response embeds the business summary with the order page URL when ordering is open, and the event case is flagged via a note field.

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?

One dense paragraph that is front-loaded with the core purpose before drilling into response fields and the event edge case. Every clause carries information, though the middle enumeration of fields is heavy and could be tightened slightly.

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 return-value burden and does so thoroughly, covering field-level contents, currency, and the event/truck edge case. It omits any mention of response size, pagination, or error behavior for an invalid subdomain, which leaves a small gap for a catalog-style read.

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% and there is a single parameter, so the schema already documents 'subdomain' with an example. The description adds no syntax, format, or validation detail beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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 ('Returns the current public menu of one business') and then enumerates the exact contents returned: item ids, names, prices, category, tags, availability flags, image URLs, and option groups. It also implicitly distinguishes itself from siblings by pointing to start_order for the id's use and by explaining the event-menu_source variant that get_upcoming_events complements.

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 clear usage context: use the returned item id in start_order, and for food-truck businesses the menu is the full catalog while daily availability lives in the upcoming-events data. It stops short of an explicit when-not-to-use or a direct contrast with get_business, so it is clear but not fully routing.

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