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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no computation method, no required inputs, no output format beyond a vague "copy-paste prompt pack with examples." A caller cannot tell whether this is a deterministic calculator or a content generator, nor what it returns.

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?

Only two sentences, but both are promotional filler ("production-ready," "you can run today," "copy-paste prompt pack") that consume the entire budget without conveying capability. The lead sentence restates the tool name instead of front-loading actual function.

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?

The tool is simple (one optional param, no output schema, no annotations), yet the description still fails to say what a call produces or how the result should be used. Sellers' language about a "repeatable workflow" does not substitute for describing the return value and invocation behavior.

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 single optional "query" parameter is fully described in the schema (100% coverage), so the schema already does the explaining. The description adds no meaning about how the query scopes the analysis, but with one documented parameter the baseline of 3 is appropriate.

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 ("fnb break even tool system") and wraps it in marketing language rather than stating what the tool actually does. It never says whether it computes a break-even point, produces a template, or generates a prompt pack, so an agent cannot distinguish it from siblings like fnb-open-calculator or menu-cost-calculator.

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 or when-not-to-use guidance, and no alternative is named despite a large set of adjacent F&B tools (fnb-roi-gate, fnb-store-diagnostic, menu-cost-calculator). The only audience hint is "marketing and operations leaders," which does not tell an agent when this tool is the right call.

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