set_node_price

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: provider-only operation, platform fee deduction, default-price reset via null, bounds enforcement, running-rental price preservation, spot-node exclusion, and user confirmation. It does not describe auth requirements, error behavior, or the response.

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 front-loaded with the core action and then adds constraints and safeguards in a compact sequence. Every sentence adds useful information, with no repetition or filler.

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 two-parameter mutation tool with no annotations and no output schema, the description covers purpose, bounds, side effects, spot-node exclusion, and confirmation guidance. It is largely complete, though it does not mention authorization requirements or expected response/error behavior.

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 substantial meaning beyond the schema for price_per_hour: USD per hour for the whole node, renter-facing price, provider net of platform fee, null default reset, and min/max constraints. node_id remains undocumented, but its meaning is self-evident from the tool name.

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: set a node's hourly price, including what the renter pays and what the provider receives. It is clear but does not explicitly differentiate this operation from the sibling update_node tool.

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 constraints: the price must fall within the node's min/max bounds, spot nodes are excluded, running rentals keep their price, and the user should confirm first. It references get_my_node for bounds but does not name an alternative for related updates.

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