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 falls short. It hints only that the deliverable is a "prompt kit with step-by-step instructions", but says nothing about what the invocation actually returns, whether the "30-day support promise" implies any runtime behavior, cost, latency, or side effects — all of which are marketing claims rather than tool behavior.

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, but the second and third ("no prompt engineering needed", "ships as a full prompt kit", "30-day support promise") are sales copy that does not help an agent decide or invoke. The front-loaded content is positioning, not purpose.

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?

A single optional parameter and no output schema keep the structural burden low, but the description still leaves the agent without the essentials: what is produced, how it differs from the extensive family of restaurant/F&B tools, and what the optional query changes. For a tool sitting among many near-duplicate siblings, that is a real gap.

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 ("Optional user query to scope the analysis."), so the schema already does the work and baseline 3 applies. The description adds nothing about how a query shapes the generated workflow or what happens when it is omitted.

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 mostly restates the name ("food delivery ops") with marketing framing — "AI-powered restaurant & brand intelligence pack", "full prompt kit", "30-day support promise" — rather than stating what the tool concretely does or returns. It gives no basis for distinguishing this from the many near-identical restaurant/food siblings such as restaurant-ops-diagnostic, fnb-store-diagnostic, takeout-menu-optimizer, or chain-restaurant-war-room.

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, no prerequisites, and no mention of alternatives. Neither a query-scoped analysis nor a no-query default invocation is explained, so an agent has no criteria for choosing this tool over the dozens of restaurant/food-ops siblings in the same namespace.

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