nodes_reset_node_traffic

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state whether resetting traffic is irreversible, what counters get cleared, whether the node is disrupted, or what permissions are required. Only the HTTP method implies a mutation, which is the thinnest possible signal.

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 short, but the content is largely boilerplate: an OpenAPI path and a 'Tags: Nodes Controller' line that add little value for an agent. Brevity here reflects under-specification rather than disciplined economy.

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 mutation tool with a required identifier, no annotations, and no output schema, the description is too thin. It omits what the operation does to existing state, any side effects, and any confirmation/permission requirements beyond what the schema already notes for 'confirm'.

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 coverage is only 50%. The 'confirm' parameter is well documented in the schema itself (including the preview-not-sent behavior), but the required 'uuid' parameter has no description in either the schema or the description. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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 gives a specific verb+resource ('Reset Node Traffic') plus the HTTP endpoint, so the basic action is understandable. However, it is essentially a restatement of the tool name plus an OpenAPI path, and it does nothing to distinguish this from close siblings like nodes_restart_node or users_reset_user_traffic. Purpose is identifiable but not sharpened.

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 versus alternatives such as nodes_restart_node, nodes_restart_all_nodes, or the bulk/user reset-traffic siblings. No prerequisites, no exclusions, no context are given. The agent must infer everything.

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