ozon_review_reply_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action itself. It does not indicate whether deletion is permanent, whether it affects related comments, what authorization is required, or what happens after deletion.

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 a single concise sentence with no filler. The parenthetical Russian translation adds some redundancy but is not obstructive, and the core meaning 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 simple two-parameter delete operation, the description is minimally viable, but it lacks important context such as irreversibility, permission requirements, or what distinguishes a reply from a comment. The absence of an output schema and annotations increases the need for such context.

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 schema description coverage is 0%, and the description adds no meaning beyond the parameter names review_id and comment_id. The names are somewhat self-explanatory, but the description does not clarify the relationship between the two IDs or what each one specifically targets.

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 clear action ('Delete') and a specific resource ('review reply'), so an agent can understand the core purpose. It does not explicitly distinguish itself from sibling tools like ozon_review_reply, but the delete verb makes the distinction mostly self-evident.

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?

No guidance is provided about when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The description implies use when a review reply must be removed, but it does not discuss related tools such as ozon_review_reply or ozon_review_comments.

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