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

The description says 'without mutating it,' but the annotations declare readOnlyHint: false, which suggests the tool may mutate state. This is a direct annotation contradiction. The description also does not disclose what validation checks are performed, what side effects may occur, or what the output looks like.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core action and a meaningful constraint. However, it is so terse that it sacrifices useful context that could be included without much length.

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?

Given there is no output schema, the description should explain what the validation returns or what 'problems' means, but it does not. The tool is low-complexity, but the annotation contradiction and missing return semantics leave the agent under-informed about expected results.

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?

The input schema has no property descriptions (0% coverage) and the description adds no parameter-level detail. 'job_posting_id' is fairly self-explanatory from its name, but 'request_id' is entirely ambiguous and its purpose is left undocumented.

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 clearly states a specific action ('Validate') and a specific resource ('a draft job posting'), and explicitly scopes it as non-mutating. This distinguishes it from job posting create/update/publish tools, and the title reinforces the purpose without ambiguity.

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 description implies this tool is used for checking a draft before making changes ('without mutating it'), but it does not explicitly state when to use this versus alternatives like publish_preview, read, or update. No exclusions or alternative tool mentions are provided.

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