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

Annotations only declare readOnlyHint=true, and the description adds real behavior beyond that: cross-position scope, pagination via next_offset, and what the two undocumented filters actually do. It stops short of describing default ordering or result size, so 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?

Three short sentences, front-loaded with scope and payload, then paging, then filter semantics. Every clause carries information an agent needs; nothing is redundant.

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 paginated list with no output schema, the description discloses returned fields loosely ('contact data and the number of applications'), paging, and both filter behaviors. Default limit/sort are left to the schema, which covers them adequately.

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 67%; the two undescribed parameters (`search`, `starred_only`) are precisely the ones the description explains, including which fields `search` matches and that `starred_only` means the talent pool. The remaining four are already documented in the schema, so this compensates well for the gap.

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 and resource (list candidates) plus the scope 'across all job positions', which effectively distinguishes it from the sibling talenthr_list_job_position_applicants. It also names the payload fields (contact data, application count). The sibling is not named explicitly, so it falls short of 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?

Gives clear usage context: use `search` to match name/e-mail and `starred_only` to reach the talent pool, plus how to page. It does not state exclusions or explicitly point to talenthr_list_job_position_applicants when the caller wants a single position, so a 4 rather than a 5.

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