cdek_calculate_tariff

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

No annotations are provided, so the description should disclose behavioral traits. It mentions the POST endpoint but lacks details on rate limits, idempotency, side effects (e.g., does it mutate anything?), or auth requirements. For a calculation tool, it's likely read-only, but not explicitly stated.

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 header, summary, and parameter list. It is clear but could be slightly more concise (e.g., 'Package' repeated). Still efficient for the information provided.

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 complexity (7 params, 4 required) and presence of an output schema, the description adequately covers purpose and parameters. It lacks details on error handling or validation, but overall is sufficiently complete for a calculation 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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: tariff_code with examples, units for weight and dimensions, and default values. This adds significant value beyond the raw 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?

The description clearly states the tool calculates cost and delivery time for a specific tariff based on weight and dimensions. It distinguishes from sibling tools like cdek_calculate_tarifflist and cdek_all_tariffs by focusing on a single tariff code.

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 a concrete tariff but does not explicitly state when to use this vs alternatives like cdek_calculate_tariff_and_service. No exclusions or when-not-to-use guidance provided.

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