sync_gsxt_session

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

No annotations are provided, so the description carries the full burden. It usefully discloses the workflow precondition that a browser login must happen first and names the target site, but says nothing about how cookies are stored, whether an existing session is overwritten, or session lifetime.

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?

A single front-loaded sentence that states the action and its most important precondition. No filler, though it is arguably terse given the low structured-data coverage.

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?

An output schema exists, so return values need not be explained. However, with no annotations and an undocumented parameter, the definition leaves notable gaps around file format and session side effects for a stateful sync operation.

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?

Schema coverage is 0% and the single 'cookie_file' parameter has only a title with no format or path semantics. The description implies cookies are being imported but does not compensate by specifying the expected file format (JSON, Netscape, etc.).

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?

States a specific verb ('Import') and resource ('GSXT personal-login cookies'), which is clearly distinguishable from siblings like enterprise_collect or scout_sessions. It does not, however, explicitly differentiate itself from the closer sibling sync_enscan_cookies.

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 gives a usable precondition ('after browser login at shiming.gsxt.gov.cn'), which implies when the tool is invoked. It stops short of naming alternatives (e.g., sync_enscan_cookies) or stating when not to use it.

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