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

readOnlyHint=true already declares the safety profile, so the description's only added value is the organisational scoping ('of the organisation'). It says nothing about pagination, result ordering, or whether inactive locations are included — relevant because the schema exposes cursor paging.

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 short sentence with the resource front-loaded and no filler. It is arguably over-terse rather than padded, so conciseness itself is not a problem.

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 with an annotated safety profile and fully described parameters, the essentials are covered, but an agent gets no hint that results are paginated or how the org-wide scope interacts with other location-related tools. That gap keeps it at minimum-viable completeness.

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%: both 'next' (cursor semantics, first page) and 'limit' (default 100, max 1000) are fully documented in the schema. The description adds no parameter meaning beyond that, which matches the baseline.

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 locations'), and the singular sibling spokephone_get_location makes the plural/list nature distinguishable. It does not explicitly contrast itself with siblings such as get_location or list_location_users, so it stops 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?

No guidance on when to use this versus spokephone_get_location (single location) or spokephone_list_location_users. Usage is only implied by the verb 'List'; there are no prerequisites, exclusions, or alternatives named.

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