sync_enscan_cookies

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

With no annotations, the description carries the full behavioral burden. It does disclose the mutation target (config.yaml), which is useful, but says nothing about whether it overwrites existing config, where the aiqicha cookie must come from, permissions/authentication needs, or what happens when cookie_file is empty.

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 with the action first and zero filler. It is efficient, though its brevity edges toward under-specification rather than true conciseness.

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, but this is a config-mutating tool with no annotations and an undocumented parameter. The description is too thin to let an agent invoke it confidently.

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 cookie_file has zero schema description coverage, and the description only gestures at 'cookie' without explaining the expected file format, path conventions, or the meaning of the empty-string default. It does not compensate for the schema gap.

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 names a specific verb pair ('Import' + 'sync') and concrete resources ('aiqicha cookie', 'ENScan_GO config.yaml'), so an agent knows exactly what the tool manipulates. It is not differentiated from the similarly named sibling sync_gsxt_session, but the aiqicha-vs-gsxt distinction is implied by the data source.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as sync_gsxt_session for the other session source. The agent must infer timing and applicability entirely on its own.

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