cdek_all_tariffs

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 only states it returns all tariffs, but does not mention that it is a read-only GET operation, whether authentication is required, or any side effects. The simplicity of the tool mitigates this somewhat, but the description still lacks important behavioral context.

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 concise: one sentence for purpose, one for return value, and one line for the parameter. It is front-loaded with the main purpose. However, the first line is simply the endpoint URL, which is redundant with the tool name and could be omitted for brevity. Overall, it is efficient with minimal waste.

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 that an output schema exists (though not shown), the description does not need to explain return values. However, it lacks context such as authentication requirements, contractual prerequisites, or how the tariff list relates to other tools (e.g., for use in calculation). For a simple list tool, this is acceptable but not fully complete.

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?

The input schema has no parameter descriptions (0% coverage), so the description must compensate fully. It does so by explaining the meaning of the 'lang' parameter, listing allowed values ('rus', 'eng', 'zho'), and stating the default. This is clear and complete for a single parameter, adding 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?

The description clearly states 'List of available tariffs' and 'Returns all available and actual tariffs by contract.' It identifies the resource (tariffs) and the action (list). However, it does not explicitly differentiate from sibling tools like cdek_calculate_tariff, which also deal with tariffs but for cost calculation, so the distinction is implied rather than explicit.

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 the list of tariffs, but it provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or when not to use it. The context among many sibling tools suggests it may be used before tariff calculation, but this is not stated.

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