settle

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

No annotations provided, so description bears full burden. It thoroughly explains the internal process: alternating microtasks and timers, sleeping to deadlines, and three stopping conditions (empty queue, max_ms, max_iters). Defaults are also specified.

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 sentences only, each serving a distinct purpose: process explanation, stopping conditions, usage guidance. No unnecessary words. Front-loaded with the core action.

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?

Covers behavior and parameters thoroughly. However, it does not describe the return value or expected output. Since there is no output schema, the description should ideally mention what the tool returns (e.g., boolean or void) for full completeness.

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 description adds value by stating defaults (max_ms=2000, max_iters=50) and explaining the meaning of 'iterations' in the context of the drain loop. This supplements the schema effectively.

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?

Description uses specific verb 'Drain the JS event loop' and clearly identifies the resource and action. Unambiguously states what the tool does and distinguishes from sibling tools like 'eval' or 'click' which deal with other aspects of page interaction.

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?

Explicitly states when to use: 'Use after seeding the DOM (or after eval'd code that schedules timers) to let pending callbacks run.' This provides clear context and proper usage scenario.

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