reload

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

With no annotations, the description carries the burden of disclosing behavior. It simply states 'reload' but does not explain side effects like whether it performs a hard reload, whether it waits for the page to finish loading, or if it loses unsaved form data. This lack of behavioral detail makes it minimally transparent.

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 concise sentence with no filler. It is front-loaded, immediately conveying the core functionality. Every word 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 zero-parameter action with no annotations or output schema, the description is nearly complete. It could have added behavior context like 'waits for load' or 'does not clear the cache', but the simplicity of the tool allows the description to be sufficient as-is.

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 tool has zero parameters, and the input schema is empty, so schema coverage is 100% by default. The baseline for 0 parameters is 4, and the description adds no parameter information because none exist, which is appropriate.

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' clearly identifies the action (reload) and the target (current page). It is specific and distinguishes itself from sibling tools like navigate, go_back, and go_forward by focusing on refreshing the existing page rather than changing location.

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 reload versus alternatives such as navigate or wait_for. The context is implied but there is no explicit when/when-not or mention of alternative tools, leaving the agent to infer usage.

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