wait_for_element

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions waiting for element 'appearance' but doesn't clarify what happens when the element doesn't appear within timeout, whether this blocks execution, what the return value is (success/failure indicator), or error conditions. For a synchronization tool with potential blocking behavior, this represents significant gaps in behavioral understanding.

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 extremely concise - a single Russian phrase that directly states the tool's function. There's zero wasted language or unnecessary elaboration. While this conciseness comes at the cost of completeness, as a standalone statement it's efficiently front-loaded with the core purpose.

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 synchronization tool with 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes success/failure, what happens on timeout, whether this is a blocking call, or what (if anything) is returned. The agent would need to guess about critical behavioral aspects despite having good parameter documentation in the schema.

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%, providing good documentation for all 4 parameters. The description doesn't add any parameter semantics beyond what's in the schema - no examples of selector formats, typical timeout values, or clarification of what 'visible' means in this context. The baseline of 3 is appropriate since the schema does the heavy lifting, but the description adds no compensatory value.

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 'Ждать появления элемента' (Wait for element appearance) states a clear purpose - waiting for an element to appear. It specifies the verb 'wait' and resource 'element', but doesn't distinguish this from potential alternatives like checking for element existence or polling. The Russian translation is clear but lacks specificity about what constitutes 'appearance'.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_attributes', 'get_html', and 'get_text' that might retrieve element information, there's no indication whether this tool should be used for synchronization before those operations or as a standalone check. No prerequisites, exclusions, or comparison to similar tools are mentioned.

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