measure_interaction

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

No annotations provided, so the description carries the burden. It discloses return values (elapsed_ms, measures, interaction_to_next_paint_ms) and explains three modes and their behaviors, including a warning about fast responses. However, it does not explicitly mention side effects of the click or whether it is read-only.

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 a single paragraph that is well-structured with three modes listed, informative but not overly concise; it could be slightly more terse.

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?

Given no output schema, the description explains return values. It covers three modes thoroughly, handles complexity of timing, and is complete for a tool with 4 params (2 required).

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%. The description adds context to parameters: for wait_for it says 'measure until it appears', and for wait_for_network it explains the timing mechanics and arms before click. This adds meaning beyond schema descriptions.

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 clearly states it clicks an element and measures time until result settles, and distinguishes three modes. It is specific and distinct from sibling tools like click_element, wait_for_network, etc.

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 explicitly tells when to use each mode: 'use this for buttons whose handler fires a request asynchronously', 'measure until it appears', and 'default measures to the first network-idle window'. It also contrasts with plain network-idle.

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