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

Goes well beyond the annotations with genuinely operational detail: timeout sections return status "timeout" with partial:true and force a HOLD verdict, full price applies only when authority (broker for broker-only) is delivered, cost is $0.08 USDC on Base, and the x402 flow (402 → PAYMENT-SIGNATURE → delivery) is spelled out, including that the tool call itself is free and payment happens on the returned URL.

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?

Front-loaded with the composite purpose, then scope, then failure/pricing semantics — a sensible ordering with no filler sentences. It is dense and slightly run-on (verdict acronyms and payment mechanics packed into one paragraph), but nearly every clause carries decision-relevant 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, the description correctly carries the burden of explaining returns: an x402 URL to GET, TENDER/HOLD/REJECT verdicts derived from public fields only (explicitly no fraud score), and the timeout/partial shape. The actual delivered payload structure is only implied, but the delivery mechanism and verdict vocabulary are enough for an agent to call and interpret it.

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 the baseline is 3, but the description adds the mapping between parameters and outputs — broker_mc runs the FMCSA broker-authority check, name drives the optional OFAC screen, and mc/dot are carrier identifiers. It does not restate the 'give at least one of dot, mc or broker_mc' constraint as clearly as the schema does, but the section-to-param linkage is real added value.

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 a specific action and a well-defined composite resource: authority + SMS BASICs + broker authority + optional OFAC name screen, with the 'vet pack' framing. It is distinguishable from the granular siblings (check_carrier_authority, check_carrier_basics, check_broker_authority, screen_sanctions_name) by listing all four components in one call, though it never explicitly says 'this is the bundled alternative to those single-check 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?

'Pre-tender check' gives a clear situational context, and the description scopes which params trigger which sections ('broker authority for broker_mc', 'optional OFAC name screen'). However, it never names the cheaper single-purpose siblings as the alternative when only one check is needed, so the agent must infer when to pick this pack over them.

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