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

No annotations are provided, so the description carries the full behavioral burden, and it does substantial work: it discloses per-call price ($0.004 USDC, x402, eip155:8453), payment constraints (EOA EIP-712 only; ERC-1271/6492 unsupported), a 64 KiB MCP body cap, an experimental-price caveat and an unauthenticated-input warning. It also states key computation semantics (same-unit quantities, unknown deadlines stay unknown, future events excluded). What it omits is any explanation of the return shape or error behavior.

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 with the operation and caps front-loaded, then computation semantics, then payment/limits, then caveats. Nearly every clause carries distinct information, though the price appears twice (bracketed prefix and 'Experimental price') and the sentence packing makes it slightly harder to scan.

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 annotations, no output schema and nested input objects, the description covers inputs, pricing and trust caveats well but says nothing about what the reconciliation returns (per-order delay, status, unit-mismatch handling) or timestamp format expectations. An agent knows how to call it, but not what to expect back.

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 description coverage is 0%, so the description must compensate, and it largely does: 'as-of time' explains as_of, 'same-unit quantities' and 'deadline' map to quantity/unit/due_at, 'declared cancellation' maps to cancelled_at, 'future events are excluded' constrains delivered_at, and the 1000-item caps match maxItems. It does not specify timestamp formats (ISO 8601 vs other) or the decimal-string quantity pattern, which remain schema-only facts.

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 and resource: 'Reconcile up to 1000 supplied orders and 1000 uniquely identified delivery events at an explicit as-of time.' It names the exact scope and explains, via exclusions, what it does not do (no logistics access, reminders, penalties, refunds or proof of actual delivery), which separates it from verification-oriented siblings.

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 gives a positive trigger (reconciling declared orders against delivery events at an as-of time) and clear boundary conditions (no logistics access, no penalty/refund/proof output), but it never names an alternative sibling or says when another tool should be preferred. The guidance is implied rather than explicit.

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