ozon_map

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

Annotations already declare readOnlyHint=true, and the description adds that calling with no args returns the full map while passing an entity narrows to that entity's methods. This is useful behavioral context beyond the annotation, with no contradiction.

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?

Two short sentences front-load the purpose and immediately explain the two calling modes. Every clause earns its place; no fluff.

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, read-only map tool with one optional param and an output schema, the description covers purpose, usage, parameter semantics, and orientation guidance. Nothing an agent needs to decide whether to call it and what to pass is missing.

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 has no description for the 'entity' parameter (0% coverage), so the description carries the burden. It explains the default (no arg = whole map) and provides examples ('reviews' or stocks/prices/orders/…) that make the parameter's semantics clear, warranting a 5.

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?

States a specific purpose: a map of API entities and go-to methods. It clearly distinguishes itself from sibling tools like ozon_search_methods by framing itself as the orientation tool ('Use this before guessing'). Gives examples of entities to reinforce scope.

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?

Gives explicit when-to-use guidance: 'Use this before guessing — it orients you fast.' It also instructs how to invoke for whole map vs specific entity, but does not explicitly name alternative tools or when not to use it, so not a 5.

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