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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: trader nodes are region-bound and region is immutable after deployment, which the agent cannot learn from the schema or annotations. It stops short of stating permissions or quota limits.

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?

Three short, front-loaded sentences: action, prerequisite, then the region constraint. Every sentence carries unique information and the most consequential warning (immutable region) lands last for emphasis without padding.

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?

With an output schema present, return values need not be described, and all four required params are documented. The description covers the prerequisite tool chain and the irreversible region choice; only finer caveats (permissions, deploy duration or async behavior) are absent.

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%, with each of the four parameters already documenting its source (cloud/blockchain from get_deployment_options, project from list_projects). The description only reinforces ordering ('first') for those sources, adding marginal meaning beyond the schema — the 3 baseline applies.

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?

Opens with a specific verb+resource: 'Deploy a new blockchain node.' Clear mutation intent that separates it from sibling lifecycle tools like update_node, delete_node, and list_nodes, so an agent can route without opening a schema.

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?

Provides a concrete prerequisite ('Call get_deployment_options first for valid IDs') and a workflow rule ('Always confirm the region with the user before deploying'). It does not state when to prefer update_node over create_node, but the required-input routing is explicit and actionable.

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