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

With readOnlyHint=true already declaring the safety profile, the description adds real behavioral detail: the call returns immediately on click, otherwise yields a pending status, and the successful return includes a reference, screenshot, and build prompt. It does not mention timeouts or what happens if the user never picks, but the polling behavior is disclosed.

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?

Three short sentences, front-loaded with the core action and immediately followed by the polling rule and the return payload. No filler, though the mid-sentence 'or status pending after the wait' is slightly clunky.

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?

With no output schema, the description correctly takes on the burden of explaining returns (reference, screenshot, build prompt) plus the pending-status case. It is sufficient for an agent to call and interpret this tool, missing only edge cases like timeout/failure behavior.

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 description coverage is 100%, so both the wait duration (0-50s) and pickId provenance are already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 specific verb (wait) and resource (the user's choice on the pick page), and clarifies that it blocks until the click. It is clearly distinguishable from sibling pick_reference, which creates the pick that this tool awaits.

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?

It gives clear usage context: call it with the pickId from pickReference, and re-call it if the result is status pending. It does not explicitly name an alternative or a when-not condition, but the polling contract is spelled out well enough to drive correct invocation.

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