reloadPage

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions maintaining CDP connection and ensuring debugger statements resolve, which adds context beyond the schema. However, it doesn't specify what happens to the current page state, potential side effects (e.g., unsaved changes), or whether the operation is synchronous or asynchronous. The description covers critical workflow aspects but not all behavioral nuances.

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 fairly concise and front-loaded with the purpose, followed by usage guidance and the critical turn rule. The critical rule is highlighted with ⚠️ and CAPS, making it prominent. A slight deduction for redundancy (e.g., 'waitForSpecificPause' mentioned twice) but overall efficient.

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 the tool's moderate complexity (one optional parameter), the description covers the essential workflow context: when to call, what to do after, and why it's better than manual refresh. While it doesn't explain return values (no output schema), the description compensates with the critical turn rule and sequencing instructions. It's sufficiently complete for an agent to use the tool correctly.

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?

The schema has 100% coverage with one optional parameter (ignoreCache) already described as 'Hard reload ignoring cache (default false)'. The description doesn't add extra parameter semantics but the schema suffices. Baseline 3 is appropriate since the schema handles the parameter explanation.

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 reloads the connected page via CDP, with a specific verb ('reload') and resource ('connected page'). It distinguishes itself from a manual refresh by emphasizing reliability and CDP connection maintenance, which differentiates it from potential sibling operations like launchChrome or connect.

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?

Provides explicit when-to-use instructions: after inserting debugger; or setBreakpoint(), before waitForSpecificPause/waitForPause. It also includes a critical turn rule with clear direction to call waitForSpecificPause in the same turn, and warns against ending the turn after reloadPage. This is comprehensive guidance with specific sequencing.

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