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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the description is not carrying the safety burden. It does add that the agent runs over volume and emits a proceed/hold/reject decision, but it omits the interactive, session-scoped nature of the operation — that follow-ups resume the same conversation — which is the primary behavioral surprise here.

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 tight sentences with no filler; the core capability leads and the batch-scope qualifier follows. Nothing is wasted, though the trailing sentence is a qualifier rather than new information.

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 (score, insights, gaps, recommendation) need not be fully specified, and annotations cover the safety profile. The remaining gap is orientation against the many similarly named screening siblings, which the description does not address.

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 (message, session_userkey) are already fully documented in the schema, including the 'reuse the same value for every follow-up' instruction. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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 concrete verb and resource — evaluates candidates against job requirements and custom criteria — and enumerates what comes back (score, insights, skill gaps, proceed/hold/reject). The batch framing ('high-volume application batches') separates it somewhat from single-resume siblings, but it never names an alternative such as score_resume_against_jd or match_end_to_end, so the boundary stays inferential.

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?

'Supports high-volume application batches' implies usage on bulk application flows, but there is no explicit when-to-use, when-not-to-use, or routing to a sibling tool. The agent must infer whether to pick this over score_resume_against_jd or match_end_to_end.

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