node_wait

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

Annotations declare readOnlyHint=true and destructiveHint=false. Description adds that it never raises on timeout, always returns 'met' and 'timed_out', and describes polling behavior with intervals and caps. Almost full transparency.

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?

Concise but thorough. Front-loaded with core purpose. Every sentence adds value: behavior, polling mechanics, common uses, limitations, parameter details. No redundancy.

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 complexity (polling, timeout, states), description covers all essential aspects. Return dict fields are documented. Sibling tools are many but description handles differentiation clearly.

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%, so description carries full burden. Each parameter is explained: id_or_name, until (with default and enum), timeout_seconds, poll_interval (with default and cap behavior). No ambiguity.

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?

Explicitly states it blocks until a swarm node's Status.State reaches a target value. Lists the four possible states and common uses like waiting for 'ready' or 'down'. Distinguishes from siblings by clarifying it does not track task placement.

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 clear when-to-use guidance: after a newly joined node or while draining before removal. Also states what it does not do (track task placement) and suggests inspecting services directly for that purpose.

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