users_bulk_reset_traffic

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. 'Reset traffic' implies a destructive/mutating operation, but the description does not explain side effects, reversibility, or any permission requirements. It lacks detail about what exactly happens to the users' traffic counters.

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 short sentence, which is concise but lacks any additional structure or emphasis. It is not front-loaded with critical details, and while it is not verbose, it is too brief to be considered well-structured for an agent needing to understand the tool's role among many siblings.

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?

Given the lack of annotations and output schema, the description is insufficiently complete. It does not explain the operation's effect, any limitations, or how it differs from closely related tools like users_reset_traffic and users_bulk_all_reset_traffic. An agent could easily misuse this tool without additional 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 input schema fully documents the only parameter (userIds as an array of integers), so the description adds no extra meaning. Since schema coverage is 100%, a baseline of 3 is appropriate; the description could have added context like constraints on array size or expected ID format, but it does not.

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 the verb 'reset' and resource 'traffic' for 'selected users', which clearly indicates it resets traffic for a specified set of users. It distinguishes from users_bulk_all_reset_traffic by specifying 'selected' rather than all, but it doesn't explicitly contrast with the singular users_reset_traffic.

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 given on when to use this tool versus its siblings. The description does not mention that users_bulk_all_reset_traffic exists for resetting all users, nor does it provide any context about use cases or prerequisites. This leaves the agent to infer the scope from the parameter schema.

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