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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about what happens on invocation, what is returned (a prompt? a checklist? a plan?), or whether results are deterministic. The only behavioral claim is the vague "save hours every week," which conveys no operational information.

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 of promotional copy, none of which front-loads the actual function; "Save hours every week" occupies the leading position where the purpose statement should be. The wording is compact but not informative, so length is spent on persuasion rather than specification.

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 zero-annotation, no-output-schema tool with an optional free-text query, the description should at minimum explain what the invocation produces and how the query influences it. Instead it substitutes marketing claims, leaving an agent unable to predict the response shape or decide between this and near-identical 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?

There is a single optional parameter whose schema description already states it scopes the analysis, giving 100% coverage. The tool description adds no further meaning about how the query shapes output, so the baseline of 3 applies.

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 says the tool delivers a "battle-tested prompt and operating playbook for restaurant/brand growth," which mostly restates the name's promise in marketing language rather than stating a concrete action or output. It never explains what "guard" means here (franchise risk screening? compliance checks?) and offers no differentiation from the many sibling fnb tools such as fnb-roi-gate, fnb-store-diagnostic, or brand-fnb-playbook.

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 indication of when to use this versus the dozens of adjacent fnb/restaurant siblings, no prerequisites, and no exclusions. "No setup, works in any LLM chatbot" is a selling point, not usage guidance, so the agent is left to guess the triggering scenario.

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