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

With no annotations, the description still discloses key behavioral facts: cost of $0.01 paid in USDC on Base via x402, pre-payment validation that rejects invalid input, tariff-based (non-binding) pricing, and carrier licensing numbers. It omits response shape, quote validity period, and any rate limits, but the payment and validation disclosures are substantive.

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?

Four dense sentences, front-loaded with scope before licensing, pricing model, and payment mechanics. Every sentence carries information; only the USDOT/MC numbers are arguably filing trivia for an agent.

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 19-parameter tool with no annotations and no output schema, the description explains the pricing model and payment flow but never says what the response contains (price breakdown, validity, next step to book). That leaves a real gap around return values that no structured field covers.

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 already 100%, so the baseline is 3; the description adds real meaning by explaining that from_zip/to_zip distance selects cubic-foot long-distance pricing versus hourly local pricing only in DC/MD/VA. That framing helps an agent decide which parameter families (crew_size/est_hours vs cubic_feet/home_size) apply.

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?

States precisely what is priced: indicative household-move quotes between any two US ZIPs, with long-distance per-cubic-foot pricing and local hourly pricing confined to DC/MD/VA. The verb 'quote/pricing' and resource are clear, though it never names its sibling request_booking as the downstream step, so the distinction is only implicit.

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?

Usage context is implied by the pricing model (give ZIPs and date to get a price; local DC/MD/VA inputs trigger hourly pricing), but there is no explicit when-to-use or when-not guidance versus company_info or request_booking. The payment/validation note ('invalid input is rejected before payment') is a useful operational cue but not a selection rule.

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