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 largely fails. The one useful signal is that the output 'includes the complete prompt, usage guide, and edge-case handling', implying this returns a prompt pack rather than a computed number — which conflicts with the 'calculator' name. It says nothing about required inputs, permissions, limits, or what the agent should expect back.

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 short sentences with no padding — the flaw is not length but content. It is not front-loaded with a functional statement; the opening is a slogan rather than the capability.

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 annotations and no output schema, the description is the only source of behavioral information, and for a tool whose purpose is genuinely unclear it provides none of what an agent needs: what it produces, what the input does, or how it differs from the many fnb-* 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?

Schema description coverage is 100% for the single optional 'query' parameter, so the schema already documents it fully; baseline 3 applies. The description adds no meaning beyond the schema and never mentions the query parameter at all.

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 never states what the tool actually computes or does — 'Turn expertise into output' and 'prompt pack ... produce professional results in minutes' are marketing copy, not a verb+resource statement. The name says 'calculator' but nothing in the text says what is calculated or for which F&B scenario. With dozens of fnb-* siblings (fnb-break-even-tool, menu-cost-calculator, fnb-roi-gate), it gives zero differentiation.

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, when-not-to-use, or alternative-tool guidance appears anywhere. 'Helps restaurant and brand teams' names an audience, not a triggering condition, and no sibling is referenced for routing.

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