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

readOnlyHint=true already establishes the safety profile, and the description adds real value on top: the fields returned, plus the disclosure that kiosk codes and device ids are never exposed. It stops short of describing paging behavior or result limits, which the agent must infer from the schema.

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: what is returned, why you would call it, and one important exclusion. The return fields are front-loaded and nothing is wasted.

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, the description correctly carries the burden by enumerating the returned fields, and the schema handles pagination via next_offset. Slightly incomplete in that it does not describe response shape or how paging interacts with large result sets.

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 all ten parameters are already documented with formats, ranges and defaults. The description only implicitly relates the returned fields (email, phone, status) to the filter parameters and adds no new semantics for sort, order, limit, offset or modified_since.

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 employees (users)') and enumerates the returned fields, so the agent knows exactly what this returns. It is clearly distinguishable from every sibling, none of which list users.

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 an explicit use case: mapping user ids appearing in shifts, time activities, timesheets, time off and tasks back to names. There is no competing sibling to exclude, but it never states a when-not-to-use condition (e.g. single-user lookup) or the paging requirement for large accounts.

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