stress_test_refresh

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (refresh loop, cache bypass, assertion, pass/fail output) but lacks details on side effects, failure handling, cleanup, or whether it stops on first failure. This is adequate but not comprehensive.

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 two sentences, directly stating what the tool does and when it is useful. No filler or redundant information. Every sentence adds value.

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 six parameters, no output schema, and no annotations, the description leaves gaps. It does not describe the return format (e.g., per-iteration results structure), nor does it clarify that the assertion script is optional (the description implies it is always run). Default values and behavior for parameters like iterations, waitAfterReload, and tabId are not mentioned.

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 baseline is 3. The description adds minimal value beyond the schema, only hinting at cache bypass and assertion. It does not explain parameter behavior like default values or mutual dependencies, but the schema itself is sufficient.

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 the tool refreshes a page N times with optional assertion and cache bypass, returning pass/fail per iteration. It uses a specific verb ('Refresh') and resource ('page'), and distinguishes it from sibling tools like navigate_reload by emphasizing iteration and assertion.

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 explicit context: it is useful for catching intermittent font bugs, race conditions, and cache-dependent issues. While it does not explicitly mention when not to use it or alternatives, the context is clear enough for an agent to understand appropriate scenarios.

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