get_menu

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

No annotations provided; description does not disclose any behavioral traits such as idempotency, caching, required authentication, side effects, or rate limits. 'Load' implies read-only but this is not explicitly stated.

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?

Though only one sentence, it is under-specified and lacks critical details. The brevity is not justified by completeness; it sacrifices usefulness for shortness.

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 5 parameters and an output schema, the description fails to explain how the context works, what the menu includes, or any operational details. The absence of parameter documentation leaves users guessing.

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 0% and the description adds no information about any of the 5 parameters (merchant_id, zone_id, address_id, category_id, coordinates). The vague mention of 'linked customer and delivery context' fails to clarify parameter usage.

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?

Description states 'Load a merchant menu' which clearly indicates verb and resource. However, it does not distinguish from siblings like search_menu_items or list_restaurants, and the phrase 'using linked customer and delivery context' is vague without elaboration.

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?

No guidance on when to use this tool versus other menu-related siblings. There is no mention of prerequisites, limitations, or scenarios where alternative tools should be preferred.

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