browser_wait_for

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The word "Wait" adds the blocking semantics that annotations do not convey, which is genuine value. However, the description says nothing about timeout failure behavior, whether the wait polls or blocks, or whether the three conditions may be combined.

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?

One sentence, front-loaded with the verb and covering all three modes without padding. It is efficient, though arguably too terse given the unresolved questions about parameter exclusivity and timeout behavior.

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 three-parameter, zero-required tool with no output schema, the description is minimally viable. The notable gap is that it never states that at least one of text/textGone/time should be supplied, leaving open the possibility of a call with no arguments and no defined 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 all three parameters are already documented in the schema with their own descriptions. The description maps each clause to a parameter (appear = text, disappear = textGone, time = time), which is mildly helpful but adds no format, range, or interaction detail beyond the schema. Baseline 3 applies.

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 pairs a specific verb ("Wait for") with three concrete conditions: text appearing, text disappearing, or elapsed time. That is enough for an agent to know what the tool does without opening the schema. It does not differentiate itself from any sibling, but no sibling performs a waiting/blocking role, so the risk of confusion is low.

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 versus other tools, no mention that it is typically used to synchronize after clicks/navigation, and no statement about what happens on timeout (error vs. silent return). The agent is left to infer all of this from the name alone.

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