node_create

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. However, it does not mention any side effects, permissions, or potential destructive actions. For a creation tool, more transparency would be beneficial, but the description does not contradict any annotations.

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 extremely concise: two sentences with the purpose upfront and a clear usage hint. Every word is necessary, and the structure is optimal for quick understanding.

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 has 8 parameters, 0% schema descriptions, no annotations, and an output schema, the description is far from complete. It lacks details on required parameters, default values, and expected output, leaving significant gaps for the AI agent.

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 schema has 0% description coverage, so the description should compensate. However, only 'node_type' is given examples, while other parameters like 'properties', 'console_type', 'x', 'y', 'project_id' are not explained. This leaves the AI agent without crucial context for using the parameters correctly.

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 'Create a node directly' with examples of node_type such as vpcs, qemu, docker. It distinguishes from node_create_from_template by advising to prefer that when a template exists, making the purpose specific and well-defined.

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 explicitly advises to use node_create_from_template when a suitable template exists, providing a clear guideline on when not to use this tool. This helps the AI agent choose the correct tool among siblings.

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