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

The annotations already declare this as a read-only, non-destructive, open-world operation. The description adds useful context beyond annotations by listing returned fields and stating the 25-per-page limit and GET endpoint, though it does not discuss any auth or rate-limit constraints.

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?

The description is compact and front-loaded, covering the main action, return fields, filters, pagination, and endpoint in a few tight sentences. Every element 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?

For a list tool with annotations covering safety and a fully described parameter schema, the description supplies the essential missing return-field and pagination context. It falls just short of 5 because it does not clarify how this tool relates to papershift_get_user for single-record lookups.

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 the parameter semantics are already fully documented in the input schema. The description mentions filtering and pagination, but adds little detail beyond what the schema provides for page, location_id, working_area_id, and tag_ids.

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 uses a specific verb and resource ('List employees (users)') and names the returned fields, so the operation is clear. It does not explicitly distinguish itself from the sibling papershift_get_user, which is the main remaining ambiguity.

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?

It states that results can be filtered by location, working area, or tag, which implies typical usage. However, it gives no explicit guidance on when to use this tool versus papershift_get_user or other list endpoints, and no exclusions are provided.

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