Open X in SurfAgent to navigate to home, notifications, search, or a profile path for agent workflows.
Open X in SurfAgent. Optionally choose a starting section such as home, notifications, search, or a profile path.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Optional X path like /home, /notifications, /search?q=..., or /username. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether opening changes app state, requires prior authentication, or what happens if the path is invalid or the section fails to load.
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?
Two short sentences, front-loaded with the core action and then the optional parameter behavior. Every clause earns its place with no waste.
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 one-parameter navigation tool with no output schema, the description is adequate: it covers the action and the optional path. It falls short only in not positioning itself against the numerous sibling open_* tools.
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?
Schema description coverage is 100%, so the path parameter is already fully documented with examples. The description's mention of home, notifications, search, and profile paths largely restates the schema examples, adding little beyond them; baseline 3 applies.
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?
States a clear verb+resource: opening X in SurfAgent, and mentions it can select a starting section via path. However, it does not distinguish itself from the many overlapping siblings like x_open_home, x_open_search, x_open_notifications, and x_open_profile, which appear to be specializations of this same operation.
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 guidance on when to use this generic opener versus the dedicated section tools (x_open_home, x_open_notifications, x_open_search, x_open_profile). With so many obvious alternatives, the omission of any when/when-not routing is a real gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.