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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds context about the data source (Socrata keg4-3bc2) and that no auth is required, plus update frequency. It does not disclose details like pagination behavior or result structure, but given the annotations, a score of 3 is appropriate as the description adds some value but not extensive behavioral disclosure.

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, consisting of three sentences. It front-loads the purpose and then lists filters, followed by data coverage and source. It includes useful extras like 'No auth — US Gov public domain' without unnecessary fluff. Every sentence earns its place, so a score of 4 reflects its efficiency and clarity.

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 that an output schema exists (though not shown here) and annotations cover safety, the description is quite complete. It explains what data is available (monthly, all official land ports), update frequency, and source. It doesn't mention pagination or result limits, but the limit parameter in the schema covers that. Overall, it provides sufficient context for an agent to call the tool correctly without missing critical information.

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?

All 6 parameters have descriptions in the schema (100% coverage), including enums for border and measure. The description briefly lists filter categories but does not add format or syntax details beyond the schema. With high schema coverage, a baseline 3 is appropriate; the description adds marginal value but doesn't compensate for missing parameter info because none is missing.

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 queries monthly US border crossing statistics from a specific agency (BTS), with a specific verb ('Query') and resource. It lists filter dimensions. While it doesn't explicitly contrast with sibling tools like bts.aviation.traffic or bts.freight.indicators, its name and focus are distinct enough that an agent would likely not confuse them. A score of 4 reflects clarity without explicit sibling differentiation.

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 usage for border crossing data but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. It states data coverage and update frequency, which helps an agent understand context, but there is no guidance on choosing this tool over other BTS tools. This is adequate but not explicit.

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