cdp_reload

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action. It does not explain side effects such as page reload from network, reset of DOM state, interaction with wait_until, or prerequisites like an active session or loaded page.

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?

A single short sentence, 'Reload the current page,' is maximally concise and front-loaded. Every word earns its place; there is no redundancy or irrelevant content.

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 tool with a required session_id, an optional wait_until with four enum values, no output schema, and no annotations, a five-word description is inadequate. It lacks context about prerequisites (session/page), the meaning of wait_until, and expected behavior after invocation, making the description too thin to fully guide correct use.

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 description provides no information about the session_id or wait_until parameters. Schema coverage is 50% (wait_until has only an enum, no description). The description fails to compensate by explaining what the wait_until values mean or how they affect execution.

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 'Reload the current page' uses a specific verb ('reload') and a clear resource ('current page'), making the tool's purpose unambiguous. It naturally differentiates from sibling tools like cdp_navigate or cdp_go_back by focusing on refreshing the existing page.

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 implies usage (when you want to refresh the current page) but offers no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or contrast with sibling navigation tools, leaving the agent to infer the appropriate context.

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