bts_transport_stats

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds historical depth (data back to 1947) and lists data categories, providing useful context. However, it does not describe response structure, pagination, or any specific behavior beyond what annotations already imply, so it adds moderate but not rich transparency.

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 clear opening statement and a bulleted list of indicator categories. It is slightly long but appropriate given the breadth of data covered. The purpose is front-loaded, and there is no redundant information.

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 and only three simple parameters, the description gives a good sense of data content but lacks explicit return format or clarification on whether all indicators are returned together. The absence of an indicator selection parameter is a potential gap that could confuse an agent about how to request specific series. Given the simple parameters, this is a moderate gap.

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 all three parameters (limit, start_date, end_date) are well-documented in the schema itself. The description adds no additional parameter semantics, so it does not go beyond what the schema provides. Baseline 3 is appropriate.

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 it retrieves monthly transportation statistics and enumerates specific indicator categories (airline, transit, rail, truck, etc.), giving a precise sense of the resource. It distinguishes itself from other domain tools by its focus on transportation, though it does not explicitly differentiate from the sibling bts_border_crossings, which is a subset of this 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 provides no guidance on when to use this tool versus alternatives like bts_border_crossings or other statistical tools. It lacks any mention of exclusions, conditions, or selection criteria, leaving the agent to infer usage based solely on the title and content.

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