browser_fast_forward

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It does not mention side effects, whether it mutates state, what 'fast forward' actually does (e.g., advances a clock, speeds up animations), or any safety implications. It is entirely opaque.

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, but this is under-specification rather than effective conciseness. The sole sentence adds no valuable information beyond the tool name and thus does not 'earn its place'. The lack of structure or elaboration makes it insufficient.

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 no annotations, no output schema, and one poorly documented parameter, the description should provide comprehensive context. It provides none, leaving the tool's behavior, expected inputs, and return values completely unclear. It is inadequate for an agent to use correctly.

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 single parameter 'time' is required but the schema description coverage is 0%. The description does not explain what 'time' represents, its units, domain, or effect. Since the description does not compensate for the missing schema documentation, the agent cannot understand how to set this parameter correctly.

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 '快进时间' simply restates the tool's name ('fast forward time') without clarifying what specific action is performed or what resource is affected. It does not distinguish this tool from sibling browser_go_forward, which is about history navigation, nor does it explain the intended time-related operation.

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 or how it differs from alternatives. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent without any basis for selecting this tool over similar ones.

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