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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Records nothing' is partly redundant. What goes beyond structured data is the advisory (non-blocking) nature of warnings and the rule that same req via several agencies is acceptable while double submission is the disqualifier — real behavioral context for acting on results.

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 short sentences, front-loaded with the core action; the interpretation rule follows. Dense and mostly jargon-free apart from internal references ('JH-3', 'req'), which cost a little readability but no wasted text.

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?

No output schema exists, and the description usefully signals that the return is warnings requiring human judgment rather than a boolean block. For a 7-parameter read tool it is largely sufficient, though it omits whether matches are returned with posting ids or scores.

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 71%, so the schema carries most of the load (url, req_id, exclude_posting are undocumented strings). The description adds domain framing — that the JD body is the input being checked — but gives no guidance on which parameters drive matching or when to use exclude_posting, so it does not compensate for the gap.

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?

States a specific verb and resource: 'check a JD' as a 'duplicate guard as a pure read.' An agent can tell this is a pre-submission duplicate check and not a mutation, which implicitly separates it from hunt_add_posting. It never names a sibling explicitly, so it stops short of a 5.

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?

Gives a concrete invocation point ('before adding it') plus interpretation guidance that warnings are advisory and that agency-duplicate reqs are normal while double submission is the disqualifier. It does not name an alternative tool or an explicit when-not case, keeping it below a 5.

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