Browser Reload

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

With no annotations provided, the description carries the full burden. It explains the effect of ignoreCache=true and its real-world equivalent (Ctrl+Shift+R), which is helpful. However, it does not disclose other behavioral traits such as whether the page state is preserved, what happens to sessions, or any side effects. This is adequate but not rich.

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 concise and front-loads the core action before detailing the ignoreCache option. It wastes no words, though the parenthetical examples could be slightly redundant. Every sentence contributes to understanding.

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 reload tool with no output schema and full schema coverage, the description provides enough context to invoke it correctly, especially the ignoreCache semantics. It could mention sessionId or mode briefly, but their absence is not critical given the schema.

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 the schema already documents all three parameters. The description adds meaning for ignoreCache by clarifying the hard refresh behavior and use case, but does not mention sessionId or mode, which are documented only in the schema. The baseline is 3 when schema coverage is high.

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 and resource: 'Reload the current page.' This is unambiguous and easily distinguishable from navigation siblings like browser_navigate or browser_navigate_back. It does not explicitly differentiate from all siblings, but the purpose is clear.

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 clear context for when to use the ignoreCache option (testing a deployed change), but it does not offer explicit when-to-use vs. when-not-to-use guidance or name alternative tools for page refreshing. The implied usage is sufficient for this simple operation.

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