get_menu

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

No annotations are provided, so the description carries the full burden. It only says 'Fetch', which is synonymous with the name and adds no behavioral context beyond implying read-only. It does not disclose error behavior, return format, or any edge cases, making this a minimal disclosure.

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?

A single, concise sentence that is front-loaded with the verb and resource. There is no redundancy or unnecessary detail; every word contributes to clarity.

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?

For a simple one-parameter read operation, the description is adequate. An output schema is absent, but this is not critical for a straightforward fetch tool. The description is complete enough given the tool's simplicity, despite not specifying return values.

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?

The input schema has 100% coverage with a descriptive `id` parameter including a concrete example ('gid://shopify/Menu/123456789'). The tool description adds no further parameter meaning beyond 'by ID', but the schema already sufficiently documents the parameter, so 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?

The description 'Fetch a specific menu by ID' uses a specific verb and resource, clearly distinguishing this from get_menus (plural, for listing) and from other menu-related operations like get_menu_item. It unambiguously states the tool's function.

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 clearly implies usage when a specific menu ID is available, setting context for one-off retrieval. However, it does not explicitly mention alternatives such as get_menus for listing all menus or when not to use this tool, so it's clear but lacks explicit exclusions.

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