cluster_promote_node

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

Describes the behavioral effect: 'flips status back to OK so peers resume sending traffic/replication.' With no annotations, this is adequate but lacks details on permissions, idempotency, or what happens if node is already active.

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?

Two concise, front-loaded sentences. No filler or redundant information.

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's simplicity (2 required params, counterpart named), the description covers the essential purpose and effect. An output schema exists to cover return values, so this is reasonably complete.

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 0% and the description adds no additional meaning to cluster_id or node_id beyond their names. The tool's purpose is clear but parameter guidance is missing.

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?

Clearly states the action: 'Bring a disabled cluster node back into active service.' Names the counterpart cluster_drain_node, distinguishing it from related tools like cluster_status, cluster_sync_check, etc.

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?

Explicitly identifies as the counterpart to cluster_drain_node, implying it should be used to reverse a drain. Does not explicitly state when not to use it or provide alternatives, but the context is clear.

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