cotlet_browser_navigateOpens a public http or https address in the user's Partiful Cloud Browser and returns the URL and title it ended on. Only Partiful pages open. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | A public http or https address, e.g. https://example.com. In an app's browser, a page of that app. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/openWorld/idempotent=false/destructive=false, so the bar is lower; the description nevertheless adds real context: the final URL and title after redirects, the domain restriction ('Only Partiful pages open'), and a credit cost per started minute with a 3-minute idle timeout. Only sessions/preconditions are unstated.
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?
Three short sentences, action first, then the domain constraint, then the cost/lifecycle caveat — each sentence carries distinct information with no repetition of the schema.
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?
No output schema exists, so the description usefully says the return is the ending URL and title. Cost behavior is disclosed. Missing only the relationship to the sibling browser tools and whether a session must be opened first.
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?
Single parameter with 100% schema description coverage, so the baseline is 3. The description's 'public http or https address' duplicates the schema's format/description and adds only the domain restriction, not new syntax or semantics for the url argument.
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 specific verb (opens) and resource (a URL in the user's Partiful Cloud Browser) plus what it returns. It does not, however, distinguish itself from the sibling cotlet_browser_open, which an agent may reasonably confuse with 'navigate' — the one obvious clarity gap.
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 constraint 'Only Partiful pages open' implies when this tool is applicable, and the credit/session sentence implies operational context. But there is no explicit when-to-use versus cotlet_browser_open/cotlet_browser_click or prerequisite statement about whether a browser session must already exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.