users_reset_traffic

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the basic mutation/safety profile is already provided. The description adds no further behavioral context, such as what 'reset traffic' changes, whether usage history is lost, whether the action is reversible, or any authorization requirements.

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 only three words and contains no wasted sentences, but it is under-specified rather than appropriately concise. It fails to front-load any useful operational detail that would help an agent invoke the tool correctly.

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 traffic-reset mutation, the description omits the effect on usage data, prerequisites, and expected outcome. There is no output schema to carry return-value information, so the description should be more complete than this.

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 0%, and the description does not explain the required userId parameter at all. With only a bare number type in the schema, the description should compensate but provides no meaning, constraints, or format guidance beyond the self-descriptive parameter name.

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 and resource ('Reset user traffic'), which is clearer than a generic placeholder like 'Process'. However, it effectively restates the tool name 'users_reset_traffic' and does not distinguish the single-user operation from siblings such as users_bulk_reset_traffic or nodes_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?

The description provides no when-to-use guidance, prerequisites, or alternative tools. There is no indication of when to choose this single-user reset instead of bulk reset operations or node traffic resets.

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