Reload

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

With no annotations, the description carries the full burden and does disclose the two traits that matter most: the destructive side effect ("unsaved user input on the page is lost") and the cache-bypass behavior of ignore_cache. It does not say whether the call waits for the page load to finish, which affects a subsequent snapshot.

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?

Three short sentences, the core action front-loaded, then the flag, then the risk. Nothing is padded and each sentence contributes.

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 an action tool with no annotations and no output schema, the definition covers purpose, the cache flag, and the data-loss risk, with the fully documented schema handling targeting parameters. The one meaningful gap is whether reload blocks until load completes, which an agent needs to know before chaining reads.

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%, so the schema already documents all seven parameters including ignore_cache. The description only restates ignore_cache=true, adding no format, default, or interpretation detail beyond the schema, so the baseline 3 applies.

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?

"Reloads the page" is a specific verb+resource, and "same as Chrome reload" anchors the semantics against a well-known browser action. It is clearly distinct from browser_navigate/back/forward in intent, though it never names a sibling to route against.

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 gives no when-to-use or when-not-to-use guidance and names no alternative, so an agent comparing reload against navigate or back has nothing to select on. The destructive caution implies care but is not framed as a usage rule.

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