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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing behavioral — not what is produced, whether it mutates state, what the 30-day support promise means for a tool call, or what the response looks like. The 'ships as a full prompt kit with step-by-step instructions' line is sales copy about the product, not information an agent can act on.

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?

It is short, but every sentence is catalog copy ('no prompt engineering needed', '30-day support promise') that does no work for tool selection. Worse, it is front-loaded with an irrelevant restaurant/brand claim rather than the actual capability.

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 a vague optional input, the description had to explain what the tool produces and when to invoke it. It instead describes a purchasable prompt kit, leaving the agent with no functional understanding of the call.

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 coverage is 100%, so the schema already explains the only input; the baseline of 3 applies. The description adds nothing about how 'query' scopes output, and its phrase 'scope the analysis' appears only in the schema itself.

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 opens with 'AI-powered restaurant & brand intelligence pack,' which does not match the name ppt-write-tool and actively points the agent at the wrong domain. It then only restates the tool name ('ppt write tool workflow') without saying what the tool actually does — generate slides, draft an outline, fill a template, or something else.

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?

No when-to-use guidance, no exclusions, and no routing to the many obvious siblings (ppt-gen-tool, ppt-outline, ppt-tpl-tool, ppt-beautify). The agent is given a marketing claim instead of a decision rule, so it cannot distinguish this tool from ppt-gen-tool or ppt-write-tool's own siblings.

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