browser_submit

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

The description reveals nothing about the tool's behavior beyond the name. It does not mention side effects, prerequisites, error conditions, or what happens upon success or failure, leaving the agent without critical expectations.

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 extremely short and to the point, but it provides no structured information or additional context. It is not verbose, but it also does not add value beyond the tool name, making it minimally adequate.

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?

With no annotations, no output schema, and a one-phrase description, the tool lacks essential contextual information. An agent would not know when to prefer this over sibling tools, what inputs to provide beyond the default, or what to expect in return, making it incomplete for reliable use.

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 fully describes the only parameter 'selector' with its default value and meaning. The description adds no additional semantic detail, so the baseline score of 3 is appropriate given the high schema coverage.

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 action of submitting a form, which is a specific verb and resource. However, it does not distinguish this from other browser actions beyond the name itself, missing the differentiation that would warrant a 5.

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 is provided on when to use this tool versus other browser actions like click, fill, or evaluate. The description offers no context or examples to help an agent decide when submission is appropriate.

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