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

No annotations are provided, so the description carries the burden. It discloses that it returns navigation menus with nested children, and implies a read-only operation. However, it doesn't explicitly state that this is a read-only operation, nor does it mention any potential side effects, permissions, or rate limits. The description is adequate but not rich in behavioral detail.

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 concise and well-structured. It front-loads the purpose, lists the returned data, and provides a usage hint. The routing note is a single line that adds technical context without bloat. Every sentence earns its place.

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 the tool's simplicity (1 parameter, no output schema, no nested objects), the description is complete enough. It explains what data is returned (handle, title, item label/URL, children) and when to use it. The lack of an output schema is compensated by the description's explicit listing of returned fields. It could mention pagination or limits, but for a navigation menu list, this is likely unnecessary.

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 schema description coverage is 100% for the single parameter (companyId), which is well-documented in the schema. The description doesn't add much beyond the schema, but the schema already provides sufficient meaning. The description's mention of 'connected Shopify store' implies the companyId is used to identify the store, but this is already clear from the schema.

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 the tool lists the connected Shopify store's navigation menus with specific fields (handle, title, item label/URL, and one level of nested children). It distinguishes itself from sibling tools like list_shopify_content, list_shopify_products, and list_shopify_themes by focusing specifically on navigation menus.

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 explicitly states when to use this tool: 'Use to see the storefront's current menu structure before proposing a navigation change.' This provides clear context for usage, though it doesn't explicitly mention alternatives or when not to use it. The routing note adds technical context about the data source.

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