Return the catalog of 8 dispatch trade verticals. Per trade: the BLS OES hourly WAGE (medianRateDollars/p25/p75 — what a technician earns, NOT a price) alongside billedHourlyRateRoutineDollars, what a buyer pays hourly at routine urgency, derived by the same wage→billed transform dispatch.estimate uses. See the wage_vs_billed block. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses that no API key is required, clarifies that wages are technician earnings (not prices), and explains the derivation of billed rates via the same transform as dispatch.estimate. This adds useful behavioral context beyond a simple read operation.
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 a single dense sentence that front-loads the main purpose and efficiently packs details about the returned data fields and transformation. It is concise without being terse, though slightly longer than strictly necessary.
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 tool with no parameters and no output schema, the description provides sufficient context about what is returned (8 verticals, wage/billed rate data). It is complete enough for an agent to understand the tool's purpose and output, though it doesn't list the vertical names.
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?
There are zero parameters, so schema coverage is 100% by default. The description adds value by explaining the returned data fields (wage percentiles, billed rate) and their derivation, which goes beyond the empty schema.
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 explicitly states 'Return the catalog of 8 dispatch trade verticals,' providing a specific verb and resource. It clearly distinguishes itself from sibling tools like dispatch.estimate and dispatch.order by being the only tool that returns the catalog.
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 description implies its use for retrieving the catalog but does not explicitly guide when to use this tool versus alternatives. It mentions 'No API key required,' which is a usage hint, but lacks direct comparison to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a clearly distinct purpose: readiness probe, cost estimation, evals metrics, trade catalog, order creation, and instant quotes. The overlap between dispatch.estimate and dispatch.quote is explicitly disambiguated by authentication and purpose (keyless rate-card vs. authenticated quoted price), so there is no boundary confusion.
All tools follow a consistent dotted-prefix pattern: agentic.readiness_probe and dispatch.*, with dispatch tools all using a noun-style verb (estimate, evals, index, order, quote). No mixed conventions or irregular verbs; the naming fully supports discoverability.
Six tools is a well-scoped set for a field-service dispatch server. Each tool covers a distinct operational function without redundancy, and the count is neither too thin nor bloated for the declared scope.
The server covers pricing (estimate/quote), order creation, trade catalog, readiness probe, and performance metrics. A minor gap: there is no direct tool to fetch order status or manage/cancel orders, though a tracking URL is returned, which slightly limits lifecycle coverage.
