users_bulk_actions_bulk_all_reset_user_traffic

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

No annotations are provided, so the description carries the full burden. It implies a destructive mutation (clearing all users' used-traffic counters), but the description says nothing about irreversibility, whether it requires confirmation, permission scope, or impact on statistics/billing. Only the schema's confirm parameter hints at confirmation behavior, which is not reflected in the description itself.

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?

It is very short and front-loaded with the HTTP route, but the 'Tags: Users Bulk Actions Controller' line adds no value for an agent and the whole body is essentially a route dump rather than a structured description. Efficient in size, weak in useful structure.

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 system-wide destructive bulk operation with zero annotations and no output schema, the description far under-delivers: it offers no warning about the global blast radius, no prerequisites, and no routing vs. the two sibling reset tools. An agent could invoke this and wipe traffic counters for every user with no caution conveyed.

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 the confirm parameter is fully documented in the schema, including the Russian-language 'preview without confirm:true' behavior. Baseline 3 applies since the description adds no parameter meaning beyond the schema.

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 specific verb (reset) and resource (user traffic) scoped to ALL users via the endpoint path. It is clearly distinguishable from the sibling users_bulk_actions_bulk_reset_user_traffic (which presumably targets a subset) and users_reset_user_traffic (single user). However, the phrasing is largely a restatement of the REST route rather than a natural-language definition of purpose.

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 explicit guidance about when to use this instead of the filtered bulk reset (users_bulk_actions_bulk_reset_user_traffic) or the single-user reset (users_reset_user_traffic). The 'all' scope is implied by the name/path but never stated as a usage condition or with warnings about the blast radius of operating on every user.

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