bts_transport_stats

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

Annotations already declare readOnlyHint=true, and the description supplements this with the monthly time-series nature and the fact that some series go back to 1947. However, it does not disclose other behaviors such as output format, pagination, or rate limits, which would be valuable for a tool with no output schema.

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 well-structured with a lead sentence followed by a categorized bullet list. It front-loads the main purpose and each bullet adds distinct information, avoiding redundancy. It is longer than necessary but remains scannable and information-dense.

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?

For a tool with no output schema, the description thoroughly covers the data content (50+ indicators) and temporal range. The input parameters are fully documented in the schema. It lacks an explicit statement about the return format, but the overview is strong enough for an agent to understand the tool's scope.

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 descriptions cover 100% of the parameters (limit, start_date, end_date) with clear definitions. The tool description adds little beyond confirming 'Monthly data', so the baseline score of 3 is appropriate given high schema coverage.

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 'Get Monthly Transportation Statistics' and enumerates over 50 national indicators across multiple categories (airline, transit, rail, trucking, etc.), making the tool's purpose specific and easily distinguishable from siblings like bts_border_crossings which focuses solely on border data.

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 the tool is for broad national transportation statistics and notes monthly data since 1947, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. It does not mention sibling tools like bts_border_crossings or nhtsa_model_years, so usage guidance is only implicit.

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