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

readOnlyHint=true already tells the agent this is a safe read. The description adds the useful scope constraint that only ACTIVE employees are returned, but says nothing about pagination behavior, rate limits, or auth requirements. Adequate but not rich, given annotations cover the safety profile.

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 efficient sentences with the purpose front-loaded and zero filler; the trailing 'Housecall Pro: GET /employees' is a minor but legitimate source reference. Slightly more than strictly necessary, but well structured.

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 helpfully names the returned fields (role, contact details, permissions) and the active-only scope. Pagination semantics for page/page_size are left entirely to the schema, which is a minor gap for a list endpoint.

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 five parameters (page, page_size, sort_by, sort_direction, location_ids) are already documented at baseline. The description adds no syntax or format detail beyond the schema, so the standard baseline of 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?

States a specific verb and resource ('List the company's active employees') and enumerates what comes back (role, contact details, permissions). No sibling lists employees, so it is unambiguous against housecall_list_customers and housecall_list_jobs.

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?

'Use their ids to assign or dispatch jobs' states a downstream intent but does not explain when to call this versus alternatives, nor any preconditions apart from the implicit active-employee scope. Usage is implied rather than spelled out.

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