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

Annotations only cover the safety profile (readOnlyHint, openWorldHint), so the description carries the rest and does so well: it discloses the 0-100 match score, keyword matching semantics ('matched literally, as an ATS search would'), ATS format checks, level fit, and recruiter interview probability. It stops short of noting rate limits, input size limits, or determinism, so it is not a 5.

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 opens with the verb and resource, then lists the return payload in a compact colon-delimited series. Every clause earns its place with no filler or repetition of the name.

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, so the description carries the return-value burden and does so by enumerating every score component the caller receives. Combined with the 100%-covered input schema, an agent has everything needed to invoke and interpret the tool.

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 both parameters are already documented in the schema and the baseline is 3. The description reinforces that job_description is optional and that matching is literal/ATS-style, which is useful but adds little beyond what the schema already states.

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 uses a specific verb+resource ('Score a resume') and enumerates the exact outputs produced, which cleanly separates it from the essay/rubric/choice grading siblings whose names imply non-resume artifacts. It does not explicitly name or contrast against any sibling, so it lands at a clear-but-undifferentiated 4.

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?

'optionally against a job posting' implies the two modes of usage but never states when to prefer this tool over grade_with_rubric or the other scoring siblings. The conditional is inferable rather than explicit, and no exclusions or prerequisites are given.

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