ozon_execute_file

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

The annotations indicate readOnlyHint=false, suggesting the tool may have side effects, yet the description only mentions downloading a file (a read operation). This creates a contradiction. The description does not disclose any behavioral traits such as auth requirements, rate limits, or side effects. Therefore, it is misleading and scores low.

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 concise, with one sentence for purpose and a bullet-like list for arguments. It is front-loaded and easy to read. Every sentence contributes value.

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?

The description explains the tool's primary function and parameters, but lacks information on usage context, side effects, and differentiation from siblings. With a simple schema and output schema present, the description is adequate but not comprehensive.

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?

The description adds some meaning to parameters beyond the schema titles: it explains 'action' is an action ID, 'file_path' is a local path to save, and 'params_json' is a JSON object. However, it does not specify what actions are valid or the structure of params_json. Given that schema description coverage is 0%, the description partially compensates but remains vague.

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 states the tool executes an Ozon Seller API action that results in downloading a file. The verb 'execute' and resource 'action' are specific. However, it does not differentiate from sibling tool 'ozon_execute' which likely also executes actions but without file download. This lack of distinction prevents perfect clarity.

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 versus alternatives. There is no mention of prerequisites, context, or conditions. The sibling tools are not referenced.

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