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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds real value by disclosing that the time-clock PIN is never returned, a data-exposure constraint not derivable from annotations or 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?

Two compact sentences plus the endpoint path, front-loaded with the core action and returned fields. Every clause earns its place with no padding.

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 usefully enumerates the returned fields and adds the PIN-exclusion caveat, which is exactly the kind of detail an agent needs. It stops short of noting the default archived behavior or pagination, but those are covered by the schema.

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 four parameters (page, per_page, location_uuid, with_archived) are already documented in the schema. The description adds nothing about parameter syntax or behavior beyond the location scoping, so the 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?

The description gives a specific verb (list) and resource (employees of a location) and enumerates the returned data (contact details, job level, roles, wage type/rate, payroll id, archive date), which clearly separates it from the singular homebase_get_employee and from homebase_list_locations. It does not explicitly name the sibling it is not, so it falls just short of a 5.

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 only implied by the location scoping ("employees of a location"); there is no explicit when-to-use statement, no exclusion telling the agent to use homebase_get_employee for a single person, and no prerequisite beyond the location uuid that the schema already documents. Adequate but with clear gaps.

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