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

With no annotations supplied, the description carries the full behavioral burden, and it discloses almost nothing: it does not say what the tool returns (a prompt, a generated pack, an analysis?), whether the query scopes a returned prompt or drives an analysis, or any cost/latency/authority characteristics. "Includes the complete prompt, usage guide, and edge-case handling" hints at static content delivery but is too vague to act on.

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?

Three sentences, two of which are pure marketing filler ("Turn expertise into output", "produce professional results in minutes") that consume the front-loaded position without conveying capability. The one concrete sentence about contents is buried at the end.

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?

No annotations, no output schema, and a vague description leave the agent unable to predict what calling this tool produces or when to prefer it over the numerous sibling menu tools. For a tool whose name implies a concrete F&B analysis, this is insufficient to invoke confidently.

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?

There is a single optional parameter with 100% schema description coverage, which establishes the baseline of 3. The description adds no meaning about how "query" changes behavior or output, but the schema already documents it adequately.

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 largely restates the tool name (sanhao-menu-engineering -> "sanhao menu engineering prompt pack") and wraps it in marketing phrasing ("Turn expertise into output"). It never says what the tool actually does operationally for a menu-engineering task, and it does not distinguish itself from close siblings such as fnb-menu-engineer, restaurant-menu-engineering, menu-cost-calculator, or takeout-menu-optimizer.

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 when-to-use guidance appears — no prerequisites, no exclusions, and no routing against the many overlapping menu/F&B siblings in the list. The only context given is that restaurant and brand teams use it, which is audience framing rather than invocation guidance.

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