reload

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

No annotations exist, so the description fully bears the burden. It only says 'refresh current page' without disclosing behavioral traits like whether it discards unsaved data, triggers network requests, or affects page history. Minimal transparency.

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?

Single sentence, front-loaded with the action. Minimal and to the point. However, it is in Chinese which may reduce clarity for English-only agents, but conciseness is high.

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?

Given the simplicity (no parameters, no output schema), the description is adequate but could be improved by noting effects like page state reset. It provides the core action but lacks completeness for a tool with sibling tools that have richer descriptions.

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?

With zero parameters and 100% schema coverage, the description adds no param details, which is acceptable since there are none. Baseline score of 4 because no additional value needed.

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 '刷新当前页面' means 'refresh the current page', which is a clear and specific verb-resource pair. It distinguishes from siblings like back, forward, and navigate. However, it is a tautology of the tool name 'reload' but adds the context of '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?

No guidance on when to use reload versus alternatives like navigate or wait_for_url. No exclusions or context provided. The description simply states the action without usage advice.

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