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 does at runtime, what it returns, or what the 'refund board' artifact contains. The '30-day support promise' and 'ships as a full prompt kit' are commercial claims, not behavioral traits of an invocation.

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 badly front-loaded, leading with an 'intelligence pack' framing and burying any functional claim. Every clause is sales copy ('instantly,' 'no prompt engineering needed,' '30-day support promise') that fails to earn its place in a tool definition.

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 is the only source of truth about this tool's behavior, and it supplies none of it. An agent cannot infer what it will receive back from a 'refund board tool workflow,' nor how it differs from the dozen refund-* siblings.

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% for the single optional 'query' parameter, so the schema already documents its meaning and the description neither adds nor subtracts from it. Baseline 3 applies when the schema does the 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?

The description says it will 'instantly generate a ready-to-use refund board tool workflow,' which restates the tool name rather than defining what a refund board is or what the tool actually produces. 'AI-powered restaurant & brand intelligence pack' is category marketing, not a verb-plus-resource statement, and it does not distinguish this tool from siblings like refund-analyze-tool or refund-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 guidance on when to use this tool, no prerequisites, and no reference to any of the many refund-* siblings it overlaps with. The only usage-adjacent claim is 'no prompt engineering needed,' which tells an agent nothing about selection criteria.

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