nodes_create_node

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, yet it only implies mutation via "Create"/POST. It does not disclose that creation requires a config profile, whether the new node starts enabled, permissions needed, or that omitting confirm:true returns a dry-run preview instead of executing. For a mutating tool with zero annotation coverage this is a significant 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?

It is short and front-loaded with the action, which is good, but the raw endpoint path and the "Tags: Nodes Controller" line are auto-generated filler that add no decision-relevant value. Brevity here reflects under-specification rather than discipline.

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 create operation with a deeply nested, largely undocumented request body, no output schema, no annotations, and a hidden confirmation/preview mechanism, the description is essentially empty. An agent cannot reliably call this tool correctly from what is written.

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 description adds nothing about either parameter. The confirm parameter happens to be documented in the schema, but the large nested body object (name, address, configProfile, ips, tags, traffic settings, etc.) has no field-level documentation, and schema description coverage is only 50%. The description does not compensate for that 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 states a specific verb and resource ("Create a new node") and adds the raw endpoint POST /api/nodes, so the basic action is identifiable. However, it offers no differentiation from the many sibling node operations (nodes_update_node, nodes_delete_node, nodes_bulk_nodes_actions) and no hint of what a "node" is or what creating one entails. It is the minimum viable statement of purpose.

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, no prerequisites (e.g. that a configProfile and an active config profile UUID must exist first), and no mention of the confirm gate. The agent is left to infer everything from the schema.

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