wait_form_closed

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

With no annotations provided, the description must disclose behavior. It states 'wait until the active form closes' but does not explain what happens on timeout, whether it returns success or failure status, or whether it throws an error. The timeout parameter implies a failure mode, but the description is silent.

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 concise, one short sentence, and the purpose is front-loaded. It is minimal but not overly verbose. However, it lacks critical detail, which reduces the value of conciseness.

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?

This is a blocking operation (wait) with a timeout, no annotations, no output schema, and moderate complexity. The description omits essential information about what happens on timeout, return values, and parameter usage, making it incomplete for correct invocation.

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 the description must explain the parameters, but it does not mention 'timeout' or 'session_id' at all. The agent cannot know what the timeout value represents (seconds? milliseconds?) or how session_id is used, making it hard to set them correctly.

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 verb 'wait' and resource 'form' are clear, and the description states the action: wait until the active form closes. However, it does not specify which form is 'active' or how this relates to the session, and it doesn't distinguish itself from sibling tools like 'wait_form', 'wait_window', or 'wait_object'.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list includes 'wait_form' and 'wait_window', but the description does not explain the difference. An agent cannot decide between them based on this description.

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