Wait for user prompt

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the blocking/timeout behavior itself: it blocks, defaults to 120s with a 600s cap, and returns {timeout: true} on expiry. It also explains that the 'selection' field is what 'this' refers to in the prompt, which is behavioral context nothing else supplies. Minor gap: no discussion of what happens if the editor is closed or never opened.

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?

Front-loaded with the blocking behavior and return shape, then the loop guidance and timeout advice. Dense but nearly every clause carries information; the em-dash parentheticals add slight visual load but no wasted sentences.

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?

There is no output schema, and the description fully covers the return shape ({text, selection, seq}) and the timeout return, plus the single parameter's practical use. Nothing an agent needs to call this correctly and interpret the result is missing.

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% and already documents the default 120 and max 600, so the description re-states some of it. It does add meaning beyond the schema by explaining why you'd choose a smaller timeoutSec (client request timeout limits), which is a usage rationale the schema lacks.

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?

States a specific blocking verb and the exact trigger ('Block until the user presses Alt+Space in the Elementor editor and submits a prompt'), plus what it returns. It also disambiguates from the sibling tool agent_say by describing the report-then-wait loop.

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?

Gives explicit when-to-use guidance ('Use it for tag-team work: finish a task, call agent_say to report, then wait for the next prompt in a loop') and an operational caveat with an alternative strategy (pass a smaller timeoutSec and call again if the client enforces a short request timeout).

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