browser_set_system_time

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without detailing side effects, scope, persistence, or dependencies. The agent cannot infer what setting the system time actually changes or whether it interacts with clock-related tools.

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, which might be considered concise, but it under-specifies the tool to the point of being insufficient. This is under-specification rather than effective conciseness, as it omits critical 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?

For a mutation tool with no annotations, no output schema, and a poorly described parameter, the description is incomplete. An agent cannot understand the full context, including whether setting the time requires any special setup or affects other browser operations.

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 defines a single 'time' parameter with type number|string, but the description gives no explanation of the expected format, units, timezone, or meaning. With 0% schema description coverage, the description fails to compensate, leaving the parameter semantics entirely unexplained.

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 '设置系统时间' (set system time) clearly states a specific verb and resource, making the tool's primary function obvious. However, it does not explain how this relates to similar sibling tools like browser_install_clock or browser_fast_forward, limiting differentiation.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent without any contextual usage direction.

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