Opens a dedicated Chrome profile for direct sign-in, keeping credentials in the browser. Use this to authenticate and enable secure access to your Teachers Pay Teachers account.
Open a dedicated Chrome profile. User signs in directly; credentials stay in the browser.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
It discloses an important behavioral detail: credentials remain in the browser. It also implies user interaction. However, it does not elaborate on the browser session lifecycle or any potential side effects beyond opening the profile, though annotations partially cover this.
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 very concise, with no filler or redundancy. It front-loads the core action ('Open a dedicated Chrome profile') and then adds the key privacy detail in one short follow-up sentence.
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 no parameters and no output schema, the description is sufficiently complete for the tool's simple purpose. It could mention what happens after sign-in or how the session is used, but that is not essential for this tool.
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 tool has zero parameters and the schema coverage is complete, so no parameter-level documentation is needed. The description adds no param detail because there is nothing to detail, matching the baseline for zero-parameter tools.
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 tool opens a dedicated Chrome profile for user sign-in and emphasizes that credentials stay in the browser. This makes its purpose obvious and distinguishes it from the sibling product-management tools.
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 implies this should be used when a user needs to authenticate before product operations, but it does not explicitly state when to use it versus alternatives or what precedes/follows it. Some guidance is present, but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.