godot_wait_for_condition

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

The only behavioral disclosure is 'Auto-wait'; the description does not state that the tool blocks until timeout, what happens when the condition is never met, or whether the scene must be running. Annotations are weak (readOnlyHint=false and no safety specifics), so the description carries a heavier burden and does not meet it.

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 a single front-loaded sentence with no filler: it names the action and the kinds of targets in one compact statement. It could not be much shorter while still conveying the tool's purpose.

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 multi-option wait/synchronization tool, one sentence is thin: it omits timeout/failure semantics and exact condition types. The detailed input schema and output schema provide invocation-level detail, so the description is adequate for tool selection but not a complete behavioral reference.

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 only high-level categories like node appearance, property thresholds, and signals, without mapping them to condition_type values, expression syntax, or expected_value. The schema's property descriptions already document each parameter meaningfully, so the description's contribution here is marginal rather than essential.

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 clear verb and resource: automatically wait until a Godot condition such as node appearance, property threshold, or signal is met. This distinguishes it from the many unrelated sibling tools. However, 'signals' is imprecise because the schema exposes no signal-specific condition type, and the description does not name the exact condition_type values.

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 phrasing implies use whenever the agent needs to block until a node, property, or expression condition is satisfied, so usage context is indirectly present. It gives no explicit when-to-use/when-not-to-use guidance and does not name alternatives, though none of the sibling tools are obvious wait equivalents.

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