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 genuinely useful behavior beyond that: the default is today in the team's timezone and results are paged. It stops short of stating page-size limits (schema caps take at 200) or anything about ordering and return shape.

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 tight sentences: behavior and default first, endpoint reference second. Nothing is padded and no sentence is wasted.

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 five-parameter read-only list tool with no output schema, the description covers what an agent needs to call it correctly: default day, timezone interpretation, and pagination. The remaining undocumented optional filters are a small gap, not a blocking one.

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 only 20% — trip_date is the one documented parameter. The description gestures at 'for a day' and 'paging', which loosely maps to trip_date and skip/take, but team_region_id and include_shipments are left completely unexplained in both schema and description, and the take cap of 200 is never surfaced.

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 stops scheduled for a day') with the scope and default (today in the team's zone), plus the underlying endpoint. It implicitly separates itself from locate2u_list_unassigned_stops and locate2u_search_stops by the word 'scheduled', but never names those siblings to make the boundary explicit.

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?

The phrase 'scheduled for a day' implies the use case (a calendar/day view of scheduled stops), but there is no explicit when-to-use guidance, no mention of when to prefer locate2u_search_stops or locate2u_list_unassigned_stops, and no prerequisites or auth notes.

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