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 and provides none of it: nothing about what invocation actually produces, whether it is read-only, what model or data it touches, cost, or latency. "Ships as a full prompt kit with step-by-step instructions and a 30-day support promise" is sales copy that describes a purchasable package, not the runtime behavior of a tool call.

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, but they are front-loaded with positioning language ("AI-powered," "intelligence pack," "30-day support promise") instead of the operational fact an agent needs. Almost every clause would need to be replaced rather than trimmed to make this useful.

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 must explain the deliverable, but it never says whether the tool returns a report, a prompt template, or a document, nor how the optional query is used. For a single-parameter tool the schema is thin enough that the description should easily have completed the picture, and it does not.

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 coverage is 100% for the single optional "query" parameter, so the schema already defines it as an optional scoping string. The description adds no further meaning to the parameter, which matches the baseline-3 rule when the schema does the documentation work.

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?

"Instantly generate a ready-to-use report writer pro workflow" mostly restates the tool name (report-writer-pro) with promotional adjectives rather than a concrete verb plus resource. The opening line, "AI-powered restaurant & brand intelligence pack," describes a bundle rather than a callable operation and offers no differentiation from the many report-* siblings (report-analyze-tool, report-tpl-tool, report-formula-tool, etc.).

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 use this tool, when to prefer a sibling like report-tpl-tool or report-diag-tool, or what prerequisites exist. The only quasi-guidance, "no prompt engineering needed," is marketing phrasing, not a usage condition.

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