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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds useful structural context about what a menu item consists of, but says nothing about whether only the header menu exists, whether an empty result is possible, or how the nested 'children' are shaped.

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 tight clause with zero filler, front-loading the resource and then the returned fields. It is a sentence fragment rather than a complete statement, but nothing in it is wasted.

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 burden of explaining return values, and it only partially does so by naming four field types without saying whether the result is a flat list or a nested tree. For a zero-parameter read tool this is adequate but leaves open questions about the response shape and about its relationship to the menu-related siblings.

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 tool takes zero parameters, so the schema is complete by definition and the baseline is 4. The description implicitly confirms there is no filtering or menu selection argument, though it could have made that explicit (e.g. that it always returns the header menu).

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 identifies the resource ('The shop's header menu') and enumerates the fields returned (label, kind, target, children), so the agent knows what it is looking at. However, it is a noun phrase rather than a stated action and never distinguishes itself from the near-identical sibling 'menu_get' (or from 'menu_set'/'set_menu'), leaving real ambiguity about which read tool to pick.

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?

There is no when-to-use guidance at all: no mention of when to call this versus menu_get, and no pointer that editing the menu is done via menu_set or set_menu. The agent must infer the read-only retrieval role purely from the name.

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