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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what the tool actually does internally, what it mutates, what it returns, or any permissions/limits. The sentences present ('ships as a full prompt kit', '30-day support promise') are marketing boilerplate with zero operational content.

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 spent on positioning and support promises ('full prompt kit with step-by-step instructions', '30-day support promise') rather than on the tool's function. The most useful information is absent, and what is present does not earn its place.

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 only a vague marketing description, an agent has no way to know what a call produces or when it is the right ppt-* tool to pick. The definition is materially incomplete for even a single-parameter tool.

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 already documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about how the query scopes the rewrite, but it does not need to given full schema coverage.

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' and then says it generates a 'ready-to-use ppt rewrite tool workflow', which restates the tool name rather than stating a concrete verb+resource action. It never says what a 'rewrite' actually does to a PPT (rewrites slide copy? rewrites deck structure?) and gives no basis to distinguish it from the many ppt-* siblings such as ppt-polish-tool, ppt-write-tool, or ppt-summary-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 when-to-use or when-not-to-use guidance at all; the only selection hint is 'no prompt engineering needed', which is a sales claim, not a usage condition. Nothing tells the agent how this differs from ppt-polish-tool or ppt-tpl-tool in the sibling list.

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