ozon_delivery_methods

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

No annotations are provided, so the description carries the full burden of disclosing behavior, but it only names a resource. It does not describe whether this is a read-only lookup, what data is returned, how pagination works, or any side effects, leaving the tool's behavior almost entirely opaque.

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 short, but this is under-specification rather than effective conciseness. A single noun phrase does replace verbose content, but it fails to earn its place because it conveys no actionable information about the tool's purpose or behavior.

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?

Even though the tool surface is simple with one optional parameter, the complete absence of purpose, return behavior, and relationship to sibling delivery/carriage tools makes the description inadequate. An agent cannot correctly decide to invoke this tool based on the provided context.

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 schema has one parameter, 'limit', with 0% schema description coverage, and the description adds no explanation of what 'limit' controls or how it relates to delivery methods. The description contributes no semantic value beyond the parameter name itself.

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 'Delivery methods (методы доставки).' is essentially a translation of the tool name and lacks any verb indicating what action is performed. It does not state whether the tool lists, retrieves, or manages delivery methods, and it does not differentiate this tool from sibling tools like ozon_carriage_delivery_list.

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 gives no indication of when to use this tool or when to prefer a sibling alternative. There is no mention of context, prerequisites, or exclusions, so an agent has no guidance on selecting this tool over related delivery/supply tools.

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