freight_parse_permit

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

No annotations are provided, so the description carries the burden. It discloses the $0.25 USDC cost and input formats (PDF or image), but doesn't describe output details, error behavior, or authentication requirements. The cost disclosure adds value, but behavioral traits beyond cost are absent.

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?

Two sentences with the main action first and cost second. Zero waste.

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 tool handles 4 input parameters and has no output schema. The description states the output is 'structured JSON' but doesn't detail the structure or guide parameter selection. The state coverage and cost are mentioned, but for a parse tool with multiple input modes, more guidance would improve completeness.

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. The description mentions PDF or image inputs, but the schema already details each parameter; no additional parameter meaning is added.

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 uses a specific verb and resource: 'Parse an oversize/overweight trucking permit (PDF or image) into structured JSON across 22 US states.' It clearly distinguishes the tool from siblings like freight_parse_bol_pod or freight_parse_w9.

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 implies a clear use case (oversize/overweight permits) but doesn't explicitly state when not to use it or mention alternatives. The context is clear enough for an agent to infer appropriate use.

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