mgmt_operation_delete

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

There are no annotations, so the description carries the full burden of disclosing side effects. It only says 'Delete operation' and does not mention irreversibility, required permissions, or effects on related resources. For a destructive operation this is a significant transparency gap.

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 short but under-specified rather than appropriately concise. It consists of a fragment and an unexplained documentation URL, with no useful structural information about the operation.

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?

With no annotations and no output schema, a delete operation needs at least an explanation of scope, side effects, and response. The description supplies none of this; the generic documentation link does not substitute for concrete operational context. An agent cannot safely infer how to invoke this correctly.

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 description coverage is 100%, so counterId, operationId, and pretty are already documented in the schema. The description adds nothing about how the parameters relate or what values are expected, but the baseline of 3 applies because the schema handles the parameter documentation.

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 is a bare fragment, 'Delete operation,' which essentially restates the tool name mgmt_operation_delete. It does not explain what an 'operation' is in Yandex Metrika or what deletion involves, so it only restates the obvious and provides no real resource context.

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 on when to use this tool instead of mgmt_operation_get, mgmt_operation_create, mgmt_operation_update, or the broader management tools. There are no stated context, prerequisites, or exclusions.

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