myob_open

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the page opens inside an existing signed-in Cloud Browser session, which tells the agent authentication is handled and no login flow is needed. It does not say what happens on failure, whether an already-open browser is required, or whether arbitrary URLs outside MYOB are permitted.

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 definition is a single front-loaded sentence with no filler, and the default URL is placed immediately after the resource it applies to. The only mild redundancy is repeating the default value already present in 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?

For a one-parameter navigation tool with no output schema and no annotations, the description covers the essentials: what it opens, in what session context, and the default target. It leaves open what the tool returns or how it reports success, which an agent would need before sequencing it with myob_read or myob_click.

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% and the single 'url' parameter already documents the https://myob.com default, so the description adds essentially no meaning beyond the schema by restating the same default. The baseline of 3 applies when the schema does all the work for a one-parameter tool.

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 states a concrete verb and resource: 'Open a MYOB page in your signed-in Cloud Browser', which distinguishes it from sibling tools like myob_click, myob_read, and myob_type by making clear this is navigation to a page rather than interaction with page content. It stops short of naming a sibling explicitly, so it sits just below the top mark.

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 phrase 'to work with invoices, bills and payments' gives a usage context, implying this is the entry point before doing invoice/bill work in the MYOB web UI. However, it offers no when-not guidance, no prerequisites beyond 'signed-in', and no explicit routing away from siblings such as myob_status or myob_guide.

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