vaultre_open

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

With no annotations, the description carries the full disclosure burden. It does add genuinely non-obvious context that the page loads inside a signed-in Cloud Browser session, which implies authentication is already handled. It does not say whether opening navigates an existing tab or creates a new one, what happens on an invalid URL, or what a successful call returns.

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?

A single sentence with the action and default URL front-loaded and no padding. The awkward "to work with manage enquiries" clause is the only wasted phrasing.

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?

This is a simple one-optional-param tool with no output schema, so the bar is low, and the purpose plus default are covered. However, without annotations or a stated return value, the agent still cannot tell whether the call yields page content, a status, or just confirmation that the page is ready for the sibling read/click 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 coverage is 100% and the single optional param already documents itself as "Page to open. Default: https://vaultre.com.au". The description restates the same default, so it adds no new meaning such as accepted URL formats, relative paths, or deep links.

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 concrete verb and resource, "Open a VaultRE page in your signed-in Cloud Browser", and names the default target URL. The intent (browser navigation into the VaultRE app for enquiries, contacts, properties and viewings) is clear enough to separate it from click/read/type siblings, though the trailing phrase "to work with manage enquiries" is grammatically garbled and adds little.

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 is the entry point for getting onto a page before using the other browser tools, but it never states when to use it versus vaultre_read, vaultre_click or vaultre_status, and gives no when-not guidance or preconditions.

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