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

With no annotations, the description carries the full behavioral burden. It does disclose a deliverable concept ('full prompt kit with step-by-step instructions', '30-day support promise'), which is some output-shape context, but says nothing about safety, side effects, auth, or how the optional query influences the result.

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?

The description is short but front-loads promotional filler ('AI-powered', 'Instantly', 'no prompt engineering needed', '30-day support promise') that does not help an agent decide or invoke. The one substantively useful clause about the prompt kit is buried in marketing copy.

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), but the description never says what the agent actually receives—whether the tool returns a prompt kit, runs an analysis, or produces a report—so it is not complete for a 'workflow generator'. No output schema exists to compensate for this 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?

Schema description coverage is 100% and the single optional 'query' parameter is documented in the schema as 'Optional user query to scope the analysis.' The description adds no further meaning about how the query scopes or shapes the generated workflow beyond the schema baseline.

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 states it will 'generate a ready-to-use sales diag tool workflow', which is a rough verb+resource, but 'sales diag tool workflow' and 'AI-powered restaurant & brand intelligence pack' are marketing phrasing rather than a concrete statement of what the tool produces. It does not differentiate itself from close siblings such as sales-analyze-tool, sales-board-tool, sales-tpl-tool, or fnb-store-diagnostic.

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 exclusions, and no naming of alternatives among the many sibling diagnostic tools. The only cues are implied by the name ('sales diag') and the phrase 'no prompt engineering needed', which is a sales claim rather than invocation guidance.

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