get_node_netstat

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only operation ('Get network statistics') but does not disclose any additional behaviors such as potential impact, permission requirements, or rate limits. There is no mention of the output format or whether it aggregates data.

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 concise, consisting of a single line and an argument list. It is front-loaded and contains no fluff. However, it could be slightly more structured with explicit sections.

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 tool's simplicity (one parameter) and the presence of an output schema, the description is partially complete. It explains the basic function but lacks usage context, such as when this tool is appropriate compared to siblings or if any node state is required.

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 parameter description 'node: The node name.' adds minimal value beyond the schema's type 'string' and parameter name 'node'. With 0% schema description coverage, the description should compensate with more detail, but it only restates the parameter's role without specifying allowed values or format.

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 clearly states the verb 'Get' and the resource 'network statistics for a node' with the qualifier 'per-interface traffic', distinguishing it from sibling tools like get_node_network (likely configuration) and get_node_network_interface (likely interface settings). However, it does not explicitly differentiate from get_node_network_interface.

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 get_node_network or get_node_network_interface. The description lacks context for when per-interface traffic statistics are needed or any prerequisites.

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