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

With readOnlyHint already declaring a safe read, the description still adds real value: default ordering ('newest first'), the pagination arithmetic ('next offset = offset + limit'), and the underlying Recruitee endpoint. It does not disclose what the response payload contains or whether a total count is returned, which keeps it below 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?

Two sentences, no filler: the primary behavior and default ordering come first, filters second, and the pagination/endpoint details last. Every clause carries information an agent can act on.

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?

For a read-only list tool with no output schema and 9 fully-described parameters, the description covers ordering, filtering, and pagination adequately. It leaves return-shape expectations and the alternate sort mode unaddressed, which are minor but real gaps.

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 100%, so the baseline is 3, but the description goes beyond the schema by explaining pagination behavior (how to compute the next offset) and mapping the filter flags to intent. It omits any explanation of the 'sort' enum values (by_last_message), so it is not fully additive.

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 opens with a specific verb+resource ('List candidates') and enumerates the filter dimensions (job, search, qualified/disqualified, ids, created_after), so an agent can grasp the scope immediately. It stops short of differentiating itself from the sibling recruitee_search_candidates, leaving that boundary implicit.

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 list of narrowing options implies when the tool is useful (broad enumeration with optional filters), but there is no explicit when-to-use guidance, no exclusions, and no pointer to recruitee_search_candidates or recruitee_get_candidate as alternatives. Usage is inferable rather than stated.

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