Reload browser page

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the core behavioral profile is covered. The description adds the key context that it operates within an existing session and preserves authentication state, which is useful. However, it does not mention potential side effects like unsaved form loss or network requests, so it adds only moderate value beyond annotations.

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 a single, well-structured sentence that conveys the action and key constraints without unnecessary words. It is concise and front-loaded.

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 action, the description covers the essential context: it must target an existing page in an isolated session and preserves authentication. The output schema exists, so return values need not be described. It could mention waiting for load or error conditions, but given the tool's simplicity and annotation coverage, it is reasonably complete.

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 0% description coverage, so the description must compensate. It mentions 'explicitly addressed page' but does not explain sessionId, pageId, or timeoutMs. The parameter names are self-explanatory, but the description adds no additional meaning about how to use them or what timeoutMs controls, making it insufficient for a tool with undocumented parameters.

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 a specific page within an existing session and auth state. The verb 'reload' is specific, and it distinguishes from navigation tools like 'navigate', 'back', and 'forward' by focusing on refreshing the current 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 by requiring an 'explicitly addressed page' in an 'existing isolated session', which tells the agent it needs a session and page already open. It provides clear context but does not explicitly name alternatives or when-not scenarios, so it stops short of a 5.

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