page_reload

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

With no annotations, the description carries the behavioral disclosure burden. It explains a non-obvious trait: reloading replays console and network activity under DevCDP observation, recovering data unavailable from before the attach. It could more explicitly warn about page state loss, but the reload semantics largely imply it.

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 with no filler. The primary action is front-loaded, and the explanatory context about post-attach reloading is directly relevant and earns its place.

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 simple one-parameter tool with no output schema, the description provides sufficient context: what it reloads, why it is useful right after attaching, and what benefit the agent gains. Nothing critical is missing.

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 input schema fully describes the only parameter (bypass_cache) with a clear description and default, so the schema already carries the parameter meaning. The description adds no extra parameter detail, which is acceptable at 100% schema coverage.

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 states a specific verb ('reload') and resource ('attached tab'), making the tool's action unambiguous. It also distinguishes itself from page_navigate by targeting the current attached tab rather than navigating elsewhere.

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 gives clear when-to-use context: right after attaching, because pre-attach console history and network traffic cannot be recovered. It does not explicitly name alternatives or exclusions, but the use case is clearly scoped and actionable.

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