ozon_perf_search_methods

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

Annotations already provide readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context beyond that: 'works in Russian and English' and 'Returns JSON list of matching endpoints (best first)'. These details help the agent understand language support and result ordering without contradicting the annotations.

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 compact and well-structured. The purpose is front-loaded, and the Args section cleanly explains each parameter. Every sentence adds value, with no filler or repetition.

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 tool with an output schema, the description covers the essentials: what it does, parameter meanings, and return format. However, it omits critical context about which API or environment it targets (OZON PERF vs. Ozon Seller), making it incomplete for an agent choosing among similar search_methods 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 so thoroughly: query is explained as free text with concrete examples ('остатки', 'stocks', 'update price'), and limit is defined with a range (1-50). This adds meaning far beyond the bare schema types.

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 states a specific verb and resource: 'Search the endpoint catalog by keyword'. It clearly conveys the tool's function, but it does not explicitly distinguish it from sibling tools like ozon_search_methods or wb_search_methods. The name includes 'ozon_perf', but the description itself lacks that differentiation.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this is for the OZON PERF API or contrast with ozon_search_methods. The only usage hint is 'works in Russian and English', which is about input language, not selection context.

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