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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description usefully discloses that the call also returns the page state afterwards — a non-obvious side effect — but omits the critical behavior on timeout: it says it 'says whether the text appeared,' yet not whether a miss raises an error or returns normally.

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?

Dense and front-loaded, with the timing constraints packed parenthetically rather than in a separate paragraph. The closing phrase 'with the same numbers' is cryptic — it likely refers to another tool's element numbering without naming it, which forces a guess.

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 carries the full burden of explaining returns, and it does so only vaguely ('the elements and text in view, with the same numbers'). The timeout-failure semantics are unaddressed, which for a wait tool is the single most operationally important detail.

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% but the schema text is nearly content-free ('At most.'), so the description genuinely adds meaning: default 5 seconds, ceiling of 20, and that `text` is optional so the timeout can be used alone. It does not explain units or resolution beyond seconds, but that is minor.

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 verb and resource ('Waits until `text` shows on the page') plus its two modes (text+timeout, or timeout only), which distinguishes it cleanly from polling-free siblings like cotlet_browser_read. It never names a sibling tool, so an agent must infer the boundary from the phrase 'for results that load slowly'.

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?

'For results that load slowly' gives a clear triggering condition for using this instead of reading immediately. It stops short of explicit when-not guidance (e.g., don't wait if content is already present, pair with cotlet_browser_find for lookups), leaving some inference to the agent.

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