reload_page

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose the non-obvious cache behavior ('By default, ignores the browser cache on reload'), which is valuable for an agent deciding whether to use it. It does not mention side effects such as losing unsaved page state, but this is fairly inherent to a reload action.

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 two short sentences with no filler. It front-loads the core action, then adds the useful browser analogy and the cache behavior. Every sentence 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?

This is a low-complexity tool: one optional boolean parameter, no required inputs, and an output schema exists. The description fully explains what the tool does and its most important behavioral nuance. It is complete enough for reliable invocation, though a brief note about when to set ignore_cache to false would make it fully exhaustive.

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 no description coverage for its only parameter, ignore_cache. The description adds that cache is ignored by default, which helps explain the default true value, but it does not explicitly state the behavior when ignore_cache is false. Thus the description partially compensates for the schema gap but leaves the parameter semantics slightly implicit.

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 uses a specific verb and resource: 'Reload the current page.' It also clarifies the action with the analogy 'Same as clicking the Reload button in the web browser,' which distinguishes it from navigation tools like go_back, go_forward, and navigate.

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 conveys when the tool is relevant by equating it to the browser Reload button, and it adds the cache behavior as a key condition. However, it does not explicitly contrast this with alternatives or state when not to use it, so usage guidance is implied rather than fully specified.

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