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

With no annotations, the description carries the behavioral disclosure burden. It states that the tool returns a list of specific metrics, but does not disclose data frequency, time range, or any limitations. The read-only nature is implied by 'Get' and 'Returns,' but additional context could improve 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 three well-structured sentences: the first states the purpose, the second enumerates the returned data series, and the third adds context about the index's economic significance. Every sentence earns its place with no redundancy.

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 simple no-parameter tool with no output schema, the description is fairly complete: it explains what the tool returns and why it matters. It could mention data granularity (e.g., monthly) or temporal coverage, but overall it covers the essential aspects for typical use.

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?

There are zero parameters, so the description does not need to explain parameter semantics. The baseline of 4 applies because there is nothing missing in terms of parameter guidance, and the description focuses appropriately on output.

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 retrieves the US freight transportation health index from the Bureau of Transportation Statistics, with a specific list of returned series (TSI, truck tonnage, rail carloadings, etc.). This highly specific resource and verb distinguish it from sibling tools such as get_economic_indicators or get_rail_freight_status.

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 indicates the tool is used by logistics companies, freight brokers, and economic analysts tracking US freight demand trends, providing some context for when to use it. However, it does not explicitly mention alternatives or when not to use it, making the guidance implicit rather than explicit.

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