cdek_calculate_tarifflist

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

No annotations exist, so the description carries full burden. It only mentions the HTTP endpoint and parameter names, lacking details on side effects, authentication, error handling, or behavior beyond the basic calculation. No information on return format or potential limitations.

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 structured with a title line, a summary sentence, and a parameter list. It is concise but could omit the redundant title line. The use of 'Args:' with bullet points is clear.

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 6 parameters (3 required) and no annotations, the description covers usage basics but omits return value details. Although an output schema exists, the description does not hint at what it contains. Behavior with invalid inputs or city resolution is unexplained.

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 0%, so the description must compensate. It lists parameters with minimal descriptions (e.g., 'Sender city name') and defaults, but adds no semantics on format, constraints, or allowed values. This is adequate but not enriching.

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 calculates cost and delivery times for all available tariffs between two cities. The verb 'calculate' and resource 'tarifflist' (all tariffs) differentiate it from siblings like cdek_calculate_tariff for a specific tariff.

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 use when all tariffs are needed, but does not explicitly state when to prefer alternatives like cdek_calculate_tariff or cdek_calculate_tariff_and_service. No when-not-to-use or exclusion criteria are provided.

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