bwiki_snapshot

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

No annotations are provided, so the description must disclose behavior. It only states the action and purpose, but does not mention whether it is read-only, whether it waits for page load, or any side effects. This is a gap for a tool with no annotations.

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 in Chinese, front-loaded with the action and resource, and ends with the purpose. No wasted words.

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 tool with no parameters and no output schema, the description is somewhat minimal. It does not mention that the snapshot is taken from the current browser page or any prerequisites, but it is adequate for a simple read-only operation. Lacks some context for complete understanding.

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 input schema is empty, so the description cannot add parameter details. With zero parameters, the baseline is 4, and there is nothing more the description needs to explain.

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 resource (HTML snapshot of BWIKI page) and the verb (获取/get), and adds the purpose of element positioning. It is distinct from unrelated siblings like navigate or edit, though it could more explicitly differentiate from get_content.

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 phrase '用于元素定位' (for element positioning) provides clear context for when to use this tool. It does not name alternatives or exclusions, but the purpose is specific enough to guide an agent.

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