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

No annotations are supplied, so the description carries the full burden, and it discloses nothing behavioral: not whether the tool reads or mutates, what inputs it consumes, what it returns, or how long it takes. The remaining sentences are sales copy ("no prompt engineering needed", "30-day support promise") that say nothing about how the tool behaves when invoked.

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, none of which front-load what the tool does; the first is unrelated boilerplate and the third is a commercial promise about prompt kits and support. The only functional-sounding sentence merely echoes the tool name, so length is spent on marketing rather than orientation.

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 sole source of information for a generation-style tool, and it leaves the agent unable to predict inputs, outputs, or effects. Nothing in it would let an agent confidently choose this over recruit-rewrite-tool or recruit-write-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?

There is a single optional parameter and the schema description coverage is 100%, so the schema already explains that "query" is an optional scoping string. The description adds no further meaning about how the query influences the polish output, but the baseline of 3 applies when the schema does the documenting.

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 leans on the tool name itself ("generate a ready-to-use recruit polish tool workflow"), which is essentially a tautology. It never states what "polish" actually does to recruitment content, nor does it distinguish this tool from the many adjacent siblings such as recruit-rewrite-tool, recruit-audit-tool, recruit-check-tool, or resume-polish-tool. The opening line about a "restaurant & brand intelligence pack" actively obscures the purpose.

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, no exclusions, and no named alternatives, despite nine other recruit-* siblings plus dozens of *-polish-tool variants that an agent must choose between. The "restaurant & brand" framing is misleading rather than merely absent, since it points at the wrong domain entirely.

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