ozon_ad_min_bids

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 behavioral disclosure. It implies a read-only lookup of minimum bids but does not explicitly state that it is non-mutating, describe the expected response, or mention pagination, authentication, or rate limits.

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 extremely short and front-loaded, with 'Minimum bids by SKU' conveying the core purpose immediately. The only minor redundancy is the Russian parenthetical 'минимальные ставки', which repeats 'Minimum bids', but it does not meaningfully hurt clarity.

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?

For a simple two-parameter lookup tool, the description plus schema covers the basic inputs adequately. However, with no output schema and no annotations, an agent is left without information about the return shape or how to distinguish this tool from related bid-related siblings.

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 does add value by listing valid payment_type values (CPC, CPO, CPC_TOP), which are absent as enums in the schema, and 'by SKU' hints at the meaning of the skus parameter. However, it does not explain the semantics of each payment_type or the expected size/format of the skus array.

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 identifies the resource as 'Minimum bids by SKU' and enumerates payment_type variants, giving an agent a clear idea of what the tool concerns. However, it lacks an explicit action verb and does not distinguish itself from closely related sibling tools such as ozon_ad_campaign_bids or ozon_ad_bids_competitive.

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 provides no guidance on when to use this tool instead of the many other ad-bidding tools in the sibling list. There are no conditions, exclusions, or alternative tool references, leaving the selection decision entirely to the agent's inference.

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