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

readOnlyHint=true already declares the safe read profile, so the description carries little burden there. It adds the assignment concept (users 'assigned to' a location, which hints at member records rather than user entities) but says nothing about pagination behavior, result ordering, or whether inactive users are included.

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?

A single compact sentence with no filler, and the scoping qualifier sits right next to the verb. Nothing to trim, though nothing is front-loaded beyond the purpose itself.

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 simple read-only list tool with only three parameters and a readOnly annotation, this is close to sufficient, but with no output schema the agent gets no hint of what a user record contains or how paging metadata is returned.

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 coverage is 67% — cursor and limit are fully documented in the schema, while locationId has no description but is self-explanatory and reinforced by the description's 'assigned to one location'. Baseline 3 applies; the description adds no syntax or format detail.

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 users') plus a scoping constraint ('assigned to one location'), which distinguishes it from the unfiltered spokephone_list_users without naming it. Clear, but the sibling differentiation is only implicit.

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 the 'one location' scoping — an agent can infer it should use this instead of the global list tool when a locationId is known. However, no alternatives are named and no exclusions or prerequisites are given.

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