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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description usefully adds that results contain no company names or contact details and that the data is live ('right now'). Remaining gaps are pagination and the limit cap, which are not disclosed.

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 with zero filler; the data payload is front-loaded and the filtering caveat follows. Every clause carries information.

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 no output schema, describing the returned fields is essential and is done, and the privacy note sets expectations. It falls short only on result volume/pagination, which matters for a board listing capped at 20 items.

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 50%: 'state' is documented in the schema, while 'limit' is not. The description adds real value by clarifying that the state filter matches either the origin or the destination, but says nothing about limit or its 1-20 range, so it only partially compensates.

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 names the resource ('open loads on the boards right now') and enumerates the returned fields (route, escort type, pay, date, link), which makes it clearly distinct from siblings like search_open_jobs and find_pilot_car_escorts. It is phrased as a content statement rather than an explicit verb, but the intent is unambiguous.

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?

Optional state filtering is explained ('a state the load starts or ends in'), giving implied usage for one parameter. There is no explicit when-to-use guidance and no reference to the sibling tools, so an agent must infer that this is the discovery tool versus find_pilot_car_escorts.

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