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

The readOnlyHint=true annotation already establishes the safety profile, so the description only needs to add context. It adds the raw endpoint (GET /shipments/unassigned) but says nothing about pagination, default result limits, whether trip_date defaults to today, or how results are ordered — all of which matter for a list tool with three optional filters.

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 with the purpose front-loaded and no filler. The endpoint restatement adds little for an agent that never sees HTTP paths, but it costs only a clause.

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 zero parameter documentation, no output schema, and no mention of result shape or pagination, an agent cannot tell how to filter or what it will receive. For a three-filter list endpoint this leaves the essential calling information missing.

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% for all three parameters (trip_date, team_region_id, pickup_within_km_distance), and the description compensates for none of them — not their formats, defaults, or combined-filter behavior. The only filter it describes, "unassigned," is not even a parameter; it is implied by the endpoint.

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?

"List shipments that no team member has yet" gives a specific verb (list) and resource (shipments) plus a clear scope qualifier (unassigned). The resource noun alone separates it from the nearest sibling, locate2u_list_unassigned_stops, though the description never names that sibling explicitly.

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?

There is no statement of when to call this versus locate2u_list_unassigned_stops, locate2u_list_shipment_notes, or a general shipment lookup. Usage is only inferable from the word "unassigned"; no prerequisites or exclusions are given.

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