nodes_reset_traffic

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutation with no stated destructiveness. The description adds nothing beyond the title: it does not say whether usage counters are zeroed irreversibly, whether in-flight accounting is lost, or whether elevated permissions are required. With annotations covering only the safety hints, this leaves a significant behavioral gap.

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?

Three words with zero waste, but also zero content; this is under-specification masquerading as brevity rather than a front-loaded, information-dense summary.

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 mutating tool with one undocumented parameter, no output schema, and minimal annotations, the definition should establish at minimum what is reset and how to identify the node. Neither is present, leaving the agent guessing at the operation's effect.

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 0% and the single required parameter, uuid, is undocumented in both schema and description. The word "Node" weakly implies uuid identifies the target node, but there is no statement of format, sourcing, or whether it is the node's UUID versus another identifier.

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 is a verbatim restatement of the tool name, adding no scope or mechanism detail. It does not clarify what "traffic" means here (usage counters, quotas, billing periods) or which node is affected, and it does not distinguish itself from nodes_restart, nodes_bulk_actions, or 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 when-to-use guidance, prerequisites, or alternative routing is provided. An agent cannot tell from this text whether resetting traffic is a per-node counter wipe versus a quota cycle reset, or when users_reset_traffic would be the correct sibling instead.

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