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

With no annotations, the description must carry the behavioral burden. It does disclose the transformation steps (rebuild, extract highlights, address concerns) and the output form (A4, big-tech style), which is genuinely useful. But it omits what inputs it needs, whether it invents content or only reworks supplied material, and any limits on iterations or length.

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?

A single front-loaded sentence that packs the role framing and the four concrete actions with no filler. The persona opener ('25-year HR manager & resume-polishing master') is stylistically inflated but occupies minimal space.

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?

For a no-annotation, no-output-schema transformation tool, the description covers the deliverable adequately. It leaves a real gap around required inputs — an agent cannot tell from the text whether the resume, target role, or job description must be provided in the query before calling.

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 only one optional parameter ('query'), and the schema already documents it at 100% coverage, so the baseline is 3. The description's phrase 'for the target role' loosely implies the query can carry role context, but it adds no syntax, format, or example beyond the schema.

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 names a concrete verb and deliverable set: 'rebuilds your resume for the target role, extracts core highlights, addresses concerns, and delivers a big-tech-style A4 resume.' That is specific enough to know what the tool returns. It does not, however, differentiate itself from the many near-identical siblings (resume-optimizer-lite, resume-optimizer-pro, resume-polish-pro, resume-coach), so an agent has no basis for picking this one over those.

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?

The only usage signal is 'for the target role,' which hints the tool is job-directed. There is no statement of when to use this versus resume-optimizer-lite/pro, resume-polish-pro, resume-audit-tool, or resume-match, and no prerequisites (e.g., whether a JD or the original resume must be supplied first).

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