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 discloses nothing: not whether it writes or reads, what data it touches, whether output is durable, or what permissions are needed. Worse, "delivered as a copy-paste prompt pack with examples" mischaracterizes an MCP tool as a static document bundle, which can actively mislead an agent about what invoking it does.

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?

Two sentences that are tight but entirely promotional — "production-ready," "run today," "copy-paste prompt pack with examples" all consume space without conveying tool semantics. Nothing is front-loaded about the actual operation, so the brevity is wasted rather than efficient.

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?

There is no output schema and no annotations, so the description is the sole carrier of meaning for a tool with a large ambiguous sibling set — and it provides none. An agent cannot determine from this text what the tool returns, what it writes, or how it differs from any recruit-* sibling.

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 coverage is 100% for the single optional `query` parameter, so the schema already documents the only input and the baseline of 3 applies. The description contributes no additional meaning about how the query scopes the operation, 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 restates the tool name ("recruit write tool system") without saying what is actually written — a job posting, offer letter, JD, outreach message, or something else. It adds audience framing ("marketing and operations leaders") and delivery framing ("prompt pack") but no specific verb-plus-resource statement, so it is essentially tautological against the title.

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 versus the ten siblings in the recruit family (recruit-gen-tool, recruit-rewrite-tool, recruit-polish-tool, recruit-reply-tool, recruit-summary-tool, recruit-tpl-tool). No prerequisites, no exclusions, no alternative routing — only a vague user persona.

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