local_ydb_add_dynamic_nodes

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

The description discloses key behaviors: it returns plans without confirm, and with confirm it starts nodes, verifies IC port in viewer/json nodelist, and checks tenant metadata. Annotations (readOnlyHint=false) align with this, and no contradiction is present.

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 sentences, front-loaded with the core action, and each sentence adds value without unnecessary detail. Efficient and well-structured.

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?

The description covers the two modes and verification steps, but lacks explicit output format details for either mode, especially when confirm=true. Given the tool's 8 parameters and complexity, slightly more detail on return values would improve completeness.

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 coverage is 100% with detailed parameter descriptions. The description adds marginal value by linking parameters to the plan/execute modes and mentioning defaults (e.g., startIndex defaults to 2), but the schema already documents each parameter adequately.

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 the tool's purpose: 'Add extra dynamic tenant nodes beyond the configured primary dynamic node, one at a time.' It also distinguishes between plan-only and execution modes, differentiating it from sibling tools like local_ydb_start_dynamic_node and local_ydb_remove_dynamic_nodes.

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 explains when to use confirm=true vs false, providing clear context for execution versus planning. However, it does not explicitly mention when not to use this tool or suggest alternatives like local_ydb_start_dynamic_node for single node additions, which would strengthen guidance.

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