freight_parse_w9

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

No annotations are present, so the description carries the burden. It discloses the cost ($0.07 USDC per call) and indicates a read-only transformation to JSON, but does not cover failure modes, input handling precedence, or potential quality issues with scans/OCR. This is useful but not comprehensive.

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?

The description is a single, front-loaded sentence that states the purpose and input formats, followed by a clear cost note. There is no filler; every piece of information earns its place.

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?

The description explains the output type (structured JSON) but does not specify that at least one input parameter must be provided or how to prioritize when multiple are supplied. Given the tool has 5 parameters and no output schema, these missing details make the description incomplete for correct 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?

The input schema already provides descriptions for all 5 parameters (100% coverage), including mode enums and input source details. The tool description adds no extra parameter-specific semantics, so the baseline of 3 applies.

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?

Description uses the specific verb 'Parse' with a clear resource ('IRS Form W-9') and a specific output ('structured vendor-onboarding JSON'). This clearly distinguishes it from sibling document parsers like freight_parse_bol_pod or freight_parse_fuel_receipt.

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 identifies the exact document type and accepted input formats (text, PDF, image), which implies when to use this tool over sibling parsers. However, it does not explicitly mention exclusions or provide guidance on choosing between the 'fast', 'llm', and 'ocr' modes, though the schema descriptions offer some help.

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