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

Annotations already carry the read-only, idempotent, open-world, and non-destructive hints, so the description needs only additive context. It supplies useful details: public domain, no authentication required, source dataset identifier (Socrata y5ut-ibwt), and weekly/monthly periodicity. This goes beyond the annotations without contradicting them.

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 a single well-structured paragraph that front-loads the purpose, gives concrete indicator examples, then covers filtering, source, and access requirements. No superfluous content or repetition; every sentence earns its place.

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 read-only data retrieval tool with five optional parameters, an output schema, and comprehensive annotations, the description covers the essential ground: what data is included, how to filter it, the source, and access constraints. The only minor gap is the lack of explicit sibling routing, but that is not critical for invoking the tool correctly.

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%, with each of the five parameters having its own descriptive text including format examples and partial-match semantics. The description only restates the filtering options ('indicator name (partial match), year, or date range') without providing additional parameter-level detail, so it adds no value beyond the schema. Baseline 3 applies.

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 the verb 'Access' with a clear resource: 'weekly and monthly supply chain performance indicators from BTS', and enumerates several indicator categories (containerized volumes, railroad dwell times, truck speeds, freight rates, etc.). This makes the tool's domain obvious logically distinct from aviation or border-crossing siblings, but it does not explicitly name alternative BTS tools when overlapping indicators like the Freight Transportation Services Index exist.

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 states what the tool does and how to filter (by indicator, year, date range), but gives no guidance about when to choose this tool over siblings such as bts.transport.tsi, bts.aviation.traffic, or bts.borders.crossings. There are no exclusions or alternative-routing instructions, leaving the selection decision to inference.

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