quote_transport

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

Explicitly states no side effects ('does not escrow resources'), validates the route, and surfaces rejection reasons. With no annotations, the description fully covers behavioral traits.

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, no wasted words, front-loaded with key purpose and outputs. Efficient and well-structured.

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?

Despite no output schema, the description details what is returned (costs, distance, time, validation). For a preview tool, it covers essential context: no side effects, validation, and usage recommendation.

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%, so baseline 3. The description adds context by explaining path as waypoint chain and resourceId/amount in preview context, though schema already provides good descriptions.

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?

Clearly states the tool previews a transport route without committing, listing specific outputs (free/paid status, distance, time, fees). Distinguishes itself from sibling 'transport' by emphasizing no side effects and use before transport.

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?

Explicitly advises 'Use it before `transport` to decide,' providing clear when-to-use guidance and implying the alternative (transport) for committing.

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