mgmt_filter_delete

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

With no annotations provided, the description must fully communicate behavioral impact. It only says 'Delete filter' – no warning of permanence, authorization requirements, or effects on related resources. The irreversible, destructive nature is implied by the verb, but no additional detail is given, leaving the behavioral risk unclear.

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 very small and puts a referral link before any content. The only actual content, 'Delete filter', restates the name and adds no value. This is under-specification rather than effective front-loaded concise writing.

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 destructive tool with two required IDs and no output schema, the description is insufficient. It fails to mention what IDs are needed, what counts as successful deletion, error cases, or any side effects. An agent would have to rely on schema alone and could easily misuse the tool without understanding the delete behavior.

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 all three parameters (counterId, filterId, pretty) already have definitions. The description adds no extra parameter meaning, so the baseline of 3 applies.

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 'https://yandex.ru/dev/metrika/ru/management/ Delete filter' – essentially a bare restatement of the tool name. It doesn't add any detail about which filter is deleted, its scope, or any effect beyond what the name already implies. This is a tautology rather than a informative purpose statement.

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?

There is no guidance on when to use this tool vs alternatives. It does not mention that it deletes a management filter, nor does it distinguish it from nearby siblings like mgmt_access_filter_delete or mention any required prior context (e.g., fetch filter first). The description gives no usage direction.

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