add_node

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

With no annotations, the description carries the full burden and discloses important behavior: it returns a Docker command containing a secret token, the node comes online only after the command runs, and then goes through a GPU check. It also states the rate limit, though it does not mention auth requirements or failure behavior.

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 purpose and return value are front-loaded, followed by operational warnings and rate limit. Every sentence adds useful information: confirmation guidance, secret-handling warning, lifecycle note, and rate limit.

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?

There is no output schema, but the description explains the key return value: a Docker command containing the node secret token. Combined with the lifecycle explanation and rate limit, it gives enough context for an agent to call the tool and handle the result safely.

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 description coverage is 100%, so the schema already documents name, os, spot, type, and available, including defaults and enums. The description reinforces that name and type should be confirmed with the user but adds little parameter detail beyond the schema; baseline 3 is appropriate.

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: add a new node to the account and return the Docker install command. The word 'new' helps distinguish it from siblings like get_node_install_command, which presumably handles existing nodes, and from list/get/update node tools.

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?

It gives clear usage context: confirm the name and type with the user first, and note the 20-nodes-per-hour limit. It does not explicitly compare against the sibling get_node_install_command, so the agent must infer that this tool is for adding a node rather than fetching a command for an existing one.

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