browser_fill

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The phrase '填写表单' merely restates the tool name and does not reveal behaviors like whether it replaces existing values, triggers events, or works on hidden elements. This is a critical gap for an interaction tool.

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?

While the description is extremely short (four Chinese characters), it is under-specification rather than conciseness. It omits necessary details and does not earn its place with substantive content. A concise description should still convey key information.

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 tool has two required parameters, no annotations, and no output schema, the description needed to explain behavior and parameters. Instead, it provides only a generic verb phrase, leaving the tool's actual operation and usage completely ambiguous. It is inadequate even for a simple tool.

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 has two required strings (selector, value) with zero description coverage. The description does not explain what the selector refers to (e.g., CSS selector, XPath) or what value means in context. It adds no meaning beyond the raw schema.

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 '填写表单' translates to 'fill out form', which provides a general verb+resource but is vague. It doesn't specify that it sets a value for a specific element via selector, nor does it differentiate from sibling tools like browser_type or browser_select which also interact with form elements.

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 offers no guidance on when to use this tool versus alternatives. It simply states 'fill out form' with no context, exclusions, or mention of sibling tools. There is no information about prerequisites or scenarios where this tool is preferred.

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