ozon_describe_method

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

No annotations provided, so description carries full burden. Discloses that $ref pointers are inlined, combinators preserved, and when knowledge layer is loaded adds rate_limit, quirks, examples, related methods. Effectively communicates behavior and output characteristics.

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?

Seven sentences, front-loaded with purpose. Every sentence adds value, no redundancy. Clear structure with parameter guidance and output details.

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?

Given existence of output schema, description does not need to detail return values but still mentions key content. Covers input, output, and conditional behavior (knowledge layer). Complete for tool discovery and correct invocation.

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 0% description coverage, so description compensates by explaining preferred parameter (operation_id), alternative (path + optional http_method), and that at least one should be provided. Adds meaning beyond schema structure.

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?

Clearly states 'Get a complete description of one Ozon API method' with specific details about return content (metadata, resolved JSON Schema, etc.). Distinct from sibling tools like ozon_call_method and ozon_search_methods.

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?

Provides explicit guidance on parameter selection: 'Provide either operation_id (preferred) OR path (+ optional http_method).' Lacks explicit 'when not to use' or comparison with alternatives, but the context is clear.

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