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

With no annotations, the description carries the full behavioral burden. It hints that the payload contains "the complete prompt, usage guide, and edge-case handling", which weakly implies a returned prompt artifact rather than an executed analysis, but it never states whether invoking the tool performs anything, returns text, or has side effects, and gives no limits or failure 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?

Only three short sentences, but the lead sentence ("Turn expertise into output") is pure filler that occupies the most prominent position, and the remaining sentences are marketing rather than specification. Brevity here reflects under-specification, not economy.

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?

For a prompt-pack tool with no annotations and no output schema, the description should say what artifact comes back, in what shape, and for what diagnostic scenario. Instead it leaves the return contract and the applicable restaurant scenario undefined, so an agent cannot predict the result before calling.

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 explains its meaning and the baseline of 3 applies. The description adds nothing about what kind of query scoping is useful 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 restates the tool name ("fnb store diagnostic prompt pack") and wraps it in generic marketing ("Turn expertise into output", "produce professional results in minutes") without naming a concrete verb or deliverable. It never distinguishes this from nearby siblings such as restaurant-ops-diagnostic, sanhao-ops-diagnostic, or fnb-store-grading-engine, all of which plausibly cover the same territory.

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 trigger conditions, no prerequisites, no named alternatives, and no indication of what a caller should pass in the optional query. The description consists entirely of promotional framing, leaving routing between this and the many diagnostic/grading siblings entirely to inference.

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