Stop a browser profile

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

Discloses that the operation is graceful, syncs data, and reports success even if the browser already exited. This complements the annotations (idempotentHint=true, destructiveHint=false) by adding specific behavioral context about the stop process. No contradiction with annotations.

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 two sentences, front-loaded with the action and clear scope. Every phrase adds value: 'gracefully', 'sync its data directory back to the cloud', and 'safe to call when the browser has already exited'. No fluff or redundancy.

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 4 parameters, no output schema, and full annotation coverage, the description answers key questions: what it does, when it is safe, and what to expect. It could mention the hard-stop risk of retryToStop, but that is covered in the input schema.

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 provides 100% coverage for all 4 parameters, so the description does not need to add parameter details. It adds no extra meaning beyond the schema, and the baseline for full schema coverage is 3.

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 uses a specific verb ('stop') and identifies the resource ('running profile') plus a key side effect ('sync its data directory back to the cloud'). It clearly distinguishes from related tools (start_profile, stop_cookie_robot) by focusing on graceful profile termination.

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?

Provides clear context on when to use the tool: to gracefully stop a profile and sync data, and it is safe even if the browser has already exited. However, it does not explicitly discuss alternatives or when not to use it (e.g., vs. hard stop via retryToStop), leaving some decision-making to the parameter descriptions.

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