Oversize Escort Hub

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

The description adds critical context beyond the safety annotations (readOnlyHint: true). It discloses major data limitations, such as the lack of verification, the withholding of contact information, and the conditional nature of availability, which are key behavioral traits of this specific data source.

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?

The description is dense and somewhat verbose, but its density is entirely justified by the necessity of providing multiple disclaimers and workflow details. It is highly functional rather than concise.

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?

The description covers the source, the output format (names/links), and every known constraint of the tool (verification status, contact availability, and listing validity). It is maximally complete for a search/discovery endpoint.

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?

While the schema covers basic types, the description clarifies the exact domain for the 'state' parameter—it must be a US state, DC, or Canadian province listed on the Oversize Escort Hub. This is crucial domain knowledge that enhances the schema's definition.

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 purpose is perfectly clear: locating pilot car escorts. It specifies the resource (escorts), the source (Oversize Escort Hub), and the constraint (by state/province), differentiating it from sibling search tools.

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?

This section is exceptionally thorough regarding limitations. It explicitly warns the agent when contact details are unavailable, when verification is not performed, and most importantly, that a listing does not equate to current availability, preventing incorrect invocations based on expectation.

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

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the content is as-of-2016, every section cites public sources, and rules vary and change by state — a staleness caveat an agent needs before quoting this material.

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 sentences, front-loaded with the resource and audience, followed by coverage list and the staleness/source caveat. No redundant restatement of the title and nothing that could be cut.

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 static reference tool with no output schema and full schema description coverage, the description supplies what an agent needs: what content exists, how it is organized (sections with sources), and the caveat that state rules supersede the text. Nothing material is 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 coverage is 100% and the single optional 'section' parameter is fully enumerated in the schema, including the omit-for-whole-guide default. The description adds no further parameter meaning, which is acceptable given the schema carries it, but earns only the baseline.

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 resource (a plain-words beginner guide to pilot car / P/EVO work) and enumerates its coverage: the job itself, escort positions, state certification, equipment, insurance, safety, and where to verify state rules. No sibling tool (find_pilot_car_escorts, search_open_jobs, search_open_loads) overlaps with reference content, so an agent can route here without opening the schema.

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?

Audience is named ('people new to pilot car / P/EVO work'), implying when to reach for it, and the closing line gives a usage caveat ('always confirm with the state'). But there is no explicit when-not guidance or named alternative for an agent that actually wants listings rather than background reading.

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

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

Annotations already declare readOnlyHint, idempotentHint, closedWorldHint and non-destructive, so the safety profile is fully covered. The description adds nothing about freshness/staleness of the facts, whether the content is a fixed document or generated, or how it is returned. For a static facts tool with full annotation coverage, this is adequate but thin.

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 sentence that front-loads the core subject and then enumerates the covered topics without filler. It is appropriately short for a no-parameter reference tool, though the embedded list makes it slightly dense.

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 parameters and no output schema, the description needs to convey what comes back, and the topic list does that in outline. It does not say the shape of the response (single document vs sections) or whether content is current, which an agent might need before relying on pricing figures.

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?

The tool takes zero parameters, so there is no parameter semantics to convey; baseline 4 applies. The description correctly implies a take-no-arguments call by framing the tool as a fixed body of reference content.

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 concretely what content the tool returns: what the platform is, its cost, how flat-rate/open-bid/5-minute bid boards work, and privacy rules. It is clear this is a static reference/FAQ lookup rather than a search. It does not differentiate from the sibling get_pilot_car_guide, which could plausibly overlap as another informational tool.

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 the sibling guide or search tools, and no prerequisites or exclusions. The only implicit signal is that it is general background information, which the agent must infer from the noun phrase.

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

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.

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.