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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context with the contact-detail gating rule ('Applicants and posters share contact details only after the company accepts'), but says nothing about ordering, pagination, or whether the list is exhaustive when `limit` is hit.

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 dense sentence that is front-loaded with the resource definition and then enumerates returned fields. Every clause carries information, though the return-field enumeration is long enough to slightly bury the one behavioral caveat at the end.

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, the enumeration of returned fields (title, company, contractor/employee, vehicle and gear, pay, schedule, base location, link) is legitimately valuable and makes the tool's yield predictable. However, the missing `limit` semantics and the absence of any routing versus sibling search tools leave the definition short for a two-param discovery tool.

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, `limit` is not. The description mentions neither parameter, so it does nothing to compensate for the undocumented `limit` (no default value, no note that results are capped at 20 or what happens beyond that). The field list describes the output shape, not the inputs.

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 opens with a specific verb+resource ('Open jobs from companies and fleets hiring pilot car / P/EVO subcontractors or drivers'), which is far more specific than the title alone. The domain (pilot car / P/EVO work) implicitly separates it from search_open_loads, but the sibling relationship is never made 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?

There is no statement of when to use this tool versus search_open_loads or find_pilot_car_escorts, and no guidance on when an agent should supply `state` or adjust `limit`. The only contextual remark — contact details are shared only after the company accepts — describes data policy, not invocation guidance.

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