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

readOnlyHint already signals a safe read, and the description adds two things annotations cannot: the payload contains personal data (a privacy/visibility caution) and the result is paged with next_page carried into the page parameter. It omits any note on volume, permissions, or total-count behavior.

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 tight sentences: field manifest first, privacy caution and alternative second, paging mechanics last. The field list is not padding because no output schema exists, so each item earns its place.

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?

With no output schema, enumerating the returned fields is exactly the right compensation, and the personal-data warning plus paging note cover the main risks. Missing only secondary context such as expected volume or whether the listing is company-wide or scoped to the caller.

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 both parameters are already documented, including the next_page-to-page convention. The description restates the paging convention but says nothing about as_of_date (point-in-time resolution), so it adds essentially no meaning beyond the schema; baseline 3 applies.

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?

Specific verb ('List') plus resource ('company's employees') and an explicit enumeration of the returned fields, including salary and contract data. It also names the lighter sibling jethr_list_employee_overviews, so an agent can distinguish this from both that tool and jethr_get_employee.

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?

Explicitly routes the agent to jethr_list_employee_overviews for a lighter payload, which is the main sibling ambiguity. It does not state when to prefer jethr_get_employee for a single record, so the guidance is clear but not exhaustive.

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