ruyi_emulate_timezone

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action without explaining side effects, persistence, page scope, or reversibility. It does not mention what happens after setting the timezone or whether it affects network requests.

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 concise but under-specified. A single phrase is not enough for a tool with two parameters and potential side effects; it sacrifices necessary detail for brevity.

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 output schema, no annotations, and incomplete schema coverage, the description is far from complete. It does not clarify the effect of pageIdx, whether the emulation persists, or how it interacts with other emulation settings. A more detailed description is needed for proper tool selection and invocation.

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 description adds no information about the timezoneId or pageIdx parameters. Schema coverage is only 50% (timezoneId documented, pageIdx missing), and the description does not compensate by explaining either parameter or how to use them.

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 a specific action (simulate) on a specific resource (browser timezone), distinguishing it from sibling emulation tools like geolocation or locale. However, it leaves ambiguity about whether the emulation applies to the whole browser or a specific page, given the pageIdx parameter.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites, effects on existing pages, or whether a page reload is needed. The description provides no contextual hints beyond the action itself.

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