get_freight_carriage

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns dispatch tons and ton-km, and that it supports date/station/item filtering, but does not mention response format, pagination, or default behavior when no filters are set. Not contradictory, but incomplete.

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?

Well-structured: a two-sentence Korean intro states purpose and capabilities, followed by a clear Args list with definitions. No redundant or filler content; front-loaded and efficient.

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?

The description covers all parameters and indicates the returned data (ton and ton-km). It leaves ambiguity about default behavior when no date filters are provided and whether station code vs name are required, and doesn't clarify output structure, though an output schema exists. Overall slightly incomplete for a 10-optional-param tool.

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 coverage is 0%, and the description compensates fully by explaining each of the 10 parameters, including format (YYYYMMDD), meaning (gte/lte), and concrete examples like '3900090'=약목. This adds significant value beyond the schema.

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?

Description clearly states the tool queries freight train transport performance (화물열차 수송실적 조회), providing dispatch tons and transport ton-km for station-to-station segments, with filtering by freight classification and item categories. This distinguishes it from siblings like get_freight_items (item list) or search_freight_code (code lookup).

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 retrieving freight performance statistics, but does not explicitly state when to use it versus alternatives or exclude certain cases. It provides context (segment-based performance with date/item filters) but no direct 'use this when' guidance.

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