Utils Invoice Extract

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds the one thing annotations cannot: this call is metered at 0.10 USD settled via x402 on eip155:8453, which is genuinely useful for cost-aware routing. It stops short of saying whether the charge is incurred on failure or what the response looks like.

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?

Short and free of padding, but the first line is a verbatim echo of the title and consumes space without adding information. The one substantive sentence (route and price) is at least present and not buried.

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?

An output schema exists, so return values need no explanation, but the description still leaves the core purpose, the meaning of the only input, and the paid-call semantics under-specified for a tool that costs money per invocation.

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 0% and the single 'text' parameter is undocumented in both schema and description, so the description does not compensate for the gap. An agent cannot tell whether 'text' means raw OCR output, pasted invoice text, or a document reference.

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 restates the tool name and adds only the transport route and price; it never says what 'extract' actually produces (line items? totals? dates?) or what it extracts from. A sibling named v1_invoice_ocr exists and is not distinguished in any way.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no mention of the closely related v1_invoice_ocr or the other v1_utils_* tools. The agent is left to infer usage entirely from the name.

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