Close MyChart Browser

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

The description discloses key behavioral traits beyond the annotations: the session is preserved on disk, only the browser process is freed, and the next call auto-relaunches. This adds significant context to the idempotent and non-destructive hints. It also clarifies side effects for the user.

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 long, front-loaded with the primary action, and contains no fluff. Every sentence adds useful information: the first states the core action, the second clarifies persistence and automatic relaunch.

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?

For a simple no-parameter tool with no output schema, the description fully covers purpose, side effects, and behavioral guarantees. It addresses the most likely user concerns—whether the login is lost and what happens after closing. Nothing essential is missing.

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?

There are no parameters, and schema coverage is 100%, so the baseline for 0 params is 4. The description cannot add more meaning about parameters because none exist, and it appropriately focuses on behavior 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 clearly states the action: 'Close the automation browser' with a specific verb and resource. This is distinct from all sibling tools, which focus on login, test results, and screenshots. There is no ambiguity about what the tool does.

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 provides clear context on when to use it: to free the browser process while preserving the login session. It also notes that the next tool call relaunches the browser, implying it can be used between operations. However, it does not explicitly mention when not to use it or alternative tools, though no direct alternative exists among the siblings.

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