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

readOnlyHint=true already declares the safety profile, and the description adds the non-obvious fact that the call returns only one page rather than all matches, plus the underlying GET /v1/employees endpoint. It stops short of saying how to iterate (the schema's pageIndex does that) or what a page looks like.

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 short sentences with the purpose first and the pagination caveat second; nothing is wasted. The first sentence is a fragment ('Team members to resolve scheduling employee IDs'), which is terse to the point of slight ambiguity.

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 paged list with a fully documented 6-parameter schema and no output schema, the description covers purpose and the key pagination limitation. Field names or result shape are left implicit, but the schema carries the calling mechanics.

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 every parameter including limit, fields, wField/wValue and pageIndex is already documented in the schema. The description adds no filtering or paging syntax of its own, so 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?

Names the resource (team members / employees) and states the concrete job it serves: resolving scheduling employee IDs. That goes beyond the title 'List employees' and gives an agent a reason to pick it, though it never names a sibling tool it is distinct from.

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?

Usage is implied by 'to resolve scheduling employee IDs', which tells the agent this is an ID-lookup step in a scheduling workflow. There is no explicit statement of when to use something else, or that this reads the raw endpoint rather than a filtered list.

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