Prepare Browser Profile

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

With no annotations, the description carries the behavioral burden and does well: it explains the copy behavior, why it reduces verification risk, the fallback to an independent profile, and the Chrome-must-be-quit prerequisite. It does not disclose whether the source Chrome profile is modified or where the copied profile is stored, which leaves a minor transparency gap.

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 reasonably front-loaded: purpose, rationale, optionality, prerequisite, error handling, and alternative are ordered logically. There is slight repetition around the one-time nature, but it remains useful rather than bloated.

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 the description does not need to explain return values. For this simple zero-required-parameter setup tool, it covers the important operational context: optionality, fallback behavior, Chrome shutdown prerequisite, and retry condition. Minor missing context includes privacy implications of copying the Chrome profile.

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 input schema fully documents the single optional force parameter, so the baseline is 3. The description does not add parameter-specific guidance beyond the schema; it focuses on setup behavior and error handling instead.

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 states a specific setup action: copying the user's everyday Chrome profile so this tool can reduce CNKI risk-control verification. It clearly distinguishes this preparation utility from the sibling paper search/read/download tools by describing a one-time browser-profile setup task.

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?

It explicitly says the tool is optional, only needs to be run once, and should be used before fully quitting Chrome. It also explains the fallback if skipped, the meaning of status=chrome_running, and the equivalent terminal command.

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