Get Ozon search filters

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, so the bar is lower. The description adds genuinely useful behavioral context: compact defaults to true and truncates long facet lists, category options include slug and url, and the tool excludes products. No contradiction with 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?

Three compact sentences deliver the key scope, default behavior, an important parameter effect, a routing alternative, and an exclusion. Every sentence earns its place and the most important information is front-loaded.

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 read-only tool with no required parameters and no output schema, this description is complete enough to support a correct call: it states what is returned, what is not returned, how the compact parameter changes payload shape, and which sibling to use for category tree browsing.

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 documentation covers all four parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining what compact=true actually truncates and what kind of option data is preserved (brand/category/price fuller, category options with slug+url).

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 identifies the resource ('filters and sort options'), states when it is relevant ('BEFORE / alongside searching'), and explicitly says it 'Does not return products,' which separates it from product-returning siblings like ozon_search. This is a specific, well-scoped purpose.

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?

It names ozon_list_categories as the alternative for browsing the category tree and frames the tool's use relative to searching. It does not explicitly say to use ozon_search when products are needed, but the statement 'Does not return products' makes that boundary reasonably clear.

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