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

With no annotations, the description carries the full disclosure burden, and it discloses almost nothing beyond the claim that a prompt, usage guide, and edge-case handling are 'included'. It doesn't describe what the tool returns (a rewrites list? a prompt pack text?), whether it mutates anything, or any limits on the input. The one behavioral signal, 'rewrite guard', is never explained.

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, all front-loaded with promotional framing ('Turn expertise into output', 'in minutes') that earns no place in a tool definition. The one concrete detail (pack contents) is buried at the end, and no operational information is delivered at all.

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 interface surface is tiny — one optional string parameter, no output schema, no annotations — so there is little structured data for an agent to rely on. That keeps the required disclosure small, but the description still fails to explain what the tool produces, which is the minimum an agent needs to select it confidently.

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 'query' parameter and the schema description covers it at 100%, so the schema already explains its meaning. The description adds no information about what the query scopes or how free-form it may be, so it neither helps nor conflicts. Baseline 3 applies for a well-documented single parameter.

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 is marketing copy ('Turn expertise into output', 'produce professional results in minutes') rather than a statement of the operation. It never says what the tool actually does with a thesis: rewrite it, guard/validate it, or return a prompt template. An agent reading this cannot tell it apart from the many other brand/restaurant prompt-pack tools in the sibling list.

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 at all — no trigger conditions, no prerequisites, and no mention of any alternative among the numerous brand-* and restaurant-* siblings. The only audience hint ('restaurant and brand teams') is a marketing segment, not an invocation criterion.

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