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

readOnlyHint=true already covers the safety profile, so the bar is lower, but the description adds nothing beyond the raw API path. It says nothing about pagination, result ordering, whether an empty result is common, or how trip_date interacts with the unassigned status.

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 short sentences, front-loaded with the purpose and with no filler. The API path sentence is marginally useful for cross-referencing docs but is the only near-redundant content.

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 this could be adequate, but with three entirely undescribed parameters and no output schema, the description leaves the agent unable to construct a correctly filtered call. It should at minimum explain the date and region filters and the optional shipment expansion.

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 0% across three parameters (trip_date, team_region_id, include_shipments), so the description carries the full burden and supplies nothing. An agent cannot tell whether trip_date filters by scheduled date, timezone, or format, nor what include_shipments embeds.

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 states a specific verb and resource ("List stops") with a clear qualifier ("that no driver has yet"), which tells an agent exactly what collection is returned. It does not, however, distinguish this from close siblings such as locate2u_list_unassigned_shipments, locate2u_list_scheduled_stops, or locate2u_search_stops.

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 word "unassigned"; there is no statement of when to call this versus search_stops or list_scheduled_stops, and no prerequisites or caveats. The endpoint reference adds no guidance about selection between siblings.

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