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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description's one extra signal is 'heuristic', which usefully warns the agent that results are approximate rather than authoritative, but it says nothing about scoring scale, thresholds, or failure modes.

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 leads with the action and then lists the checks; no filler or redundancy. The parenthetical enumeration is slightly list-like but every item is a distinct check the agent may care about.

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?

An output schema exists, so return values need not be explained, and the read-only behavior is covered by annotations. The description is complete for a two-parameter analysis tool; the only minor gap is not clarifying whether omitting jd_text degrades the keyword-coverage check.

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 description coverage is 100%, so the schema already documents both letter_text (required) and jd_text (optional, for keyword matching). The description adds no parameter-level detail, such as format, length limits, or how jd_text changes the output. Baseline of 3 is appropriate when the schema carries the load.

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 ('Perform heuristic ATS compliance checks') on a specific resource and enumerates the five checks performed (keyword coverage, word count, metrics density, parseable formatting, contact info), so the agent knows exactly what the tool does. It does not explicitly contrast itself with siblings like jd_analyzer or evidence_validator, which keeps it below 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?

There is no guidance on when to invoke this tool versus alternatives such as jd_analyzer or evidence_validator, nor any prerequisite or ordering advice. The only usage hint (jd_text being optional for keyword matching) lives in the schema, not the description. The agent must infer context from the name alone.

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