users_bulk_all_reset_traffic

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered by structured data. The description adds the meaningful scoping fact that this affects every user without exception, but it says nothing about irreversibility, permissions required, or throttling for what is effectively an irreversible mass operation.

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?

A single short sentence with zero filler and the scope qualifier front-loaded after the verb. It is efficient, though arguably undersized for a destructive all-users operation where a brief caveat would be worth the words.

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 parameters and no output schema, the structural surface is minimal, but the operation is highly destructive at maximum blast radius. The description covers what changes and the scope but omits any caution about irreversibility or confirmation, leaving it only minimally adequate for a tool that affects every user.

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 tool takes zero parameters, so there is no parameter semantics burden to carry; the baseline for a no-param tool is 4. The description appropriately avoids inventing parameter discussion.

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?

States a specific verb (reset), resource (used traffic), and an unambiguous scope qualifier (EVERY user). The 'EVERY user' wording is exactly what distinguishes it from sibling users_reset_traffic (single) and users_bulk_reset_traffic (selected subset), so an agent can route without opening any schema.

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?

Usage is only implied through the scope word 'EVERY': the agent can infer this is the all-users variant rather than the targeted variant. However, there is no explicit when-to-use/when-not-to-use statement, no warning about the scale of impact, and no named alternative.

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