refresh

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

Annotations already indicate destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the description adds no extra behavioral context. It does not mention potential side effects like losing unsaved form data or triggering re-execution of scripts, which would be useful.

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, direct sentence. It is front-loaded and contains no superfluous information. However, it could be slightly expanded to include context about parameters without losing conciseness.

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 action with two optional parameters and an output schema, the description is minimally adequate. It does not explain what happens after refresh (e.g., returns page content or success status), but the output schema may cover that. Lacks integration with sibling tools.

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 coverage is 100%, and the description adds no additional meaning beyond the schema's own descriptions for 'hard' and 'selector'. The tool description merely repeats the action without clarifying parameter choices.

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 verb 'Refresh' and the resource 'the current browser page', making the action unambiguous. It distinguishes itself from sibling tools like 'navigate' (which goes to a new URL) and 'open' (which opens a new 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?

No guidance is provided on when to use this tool versus alternatives like 'navigate' or 'reload' (if such existed). It does not specify prerequisites or conditions under which a refresh is appropriate (e.g., after form submission or state changes).

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