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

No annotations exist, so the description carries the full burden of disclosure, yet it never says what the tool actually produces or returns beyond vague packaging language ('full prompt kit with step-by-step instructions', '30-day support promise'). Side effects, determinism, expected inputs, and any output shape are entirely undisclosed, and the support-promise sentence is commercial filler rather than behavioral context.

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 which the lead (restaurant/brand intelligence) and the tail (30-day support promise) are promotional and uninformative for an invoking agent. The single useful clause is buried mid-sentence rather than front-loaded.

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, no output schema, and an unfamiliar 'check' verb shared by many siblings, the description needs to explain what a 'check' run inspects and returns. Instead it supplies sales copy, leaving an agent unable to predict the result of calling it.

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 schema fully documents the single optional 'query' parameter, so the baseline is 3. The description adds nothing about the query's scope or format and its 'no prompt engineering needed' framing suggests the parameter may be unnecessary, but that falls short of a genuine contradiction.

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 only operative phrase is 'generate a ready-to-use deploy check tool workflow', which gestures at the resource but never states a concrete verb-plus-resource operation. The opening claim, 'AI-powered restaurant & brand intelligence pack', is off-domain marketing that actively confuses what this tool does, and nothing distinguishes it from the sibling so-deploy-gen-tool or so-deploy-tpl-tool.

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 statement of when to call this versus the many siblings (so-deploy-gen-tool, so-deploy-tpl-tool, so-alert-check-tool, so-inspect-check-tool). 'No prompt engineering needed' is a sales claim, not a usage condition, and no prerequisites or exclusions are given.

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