Fastest US border crossing by all-in time

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

With no annotations provided, the description carries the burden of disclosing behavior. It explains the ranking methodology (all-in time), the data source (live CBP data across 85 ports), and the lane eligibility consideration. It does not cover error handling or data freshness, but the core behavioral aspects are transparent.

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 concise and front-loaded. Two sentences convey the purpose, scope, and a key insight without any wasted words. It is easy to scan and understand.

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?

Given the 7 parameters and no output schema, the description covers the essential aspects: what is ranked, by what metric, for which traffic types, and with live data. It does not explain the return format or error conditions, but the ranking behavior is sufficiently described for a tool of this complexity.

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 100%, so the baseline is 3. The description adds context about the all-in time metric and lane honoring, which helps interpret the parameters, but it does not add specific parameter-level details beyond the schema.

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 clearly states the tool ranks US ports of entry by all-in time (drive + wait), covering passenger, commercial, and pedestrian traffic. It distinguishes itself from the sibling tools (which are unrelated) and the note about nearest not being fastest adds a specific behavioral insight.

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 provides clear context on when to use the tool: to find the fastest border crossing by all-in time, explicitly contrasting with the nearest crossing. It does not explicitly mention when not to use it or alternatives, but the usage scenario is well implied.

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