myob_oauth_authorize_business

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

No annotations are provided, so the description carries the full burden. It says 'Start MYOB OAuth consent' but does not disclose side effects, whether it blocks, opens a browser, or requires user interaction. The parameters `open_browser` and `manual` are not explained, leaving key behavioral traits undisclosed.

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 two short sentences, front-loaded with the primary action and a brief usage note. Every word earns its place; there is no redundancy or fluff.

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?

Despite being part of an OAuth flow with related tools like myob_oauth_exchange_code, the description does not explain what happens after consent, how to use the result, or the role of the parameters. For a tool with no annotations and no output schema, this is insufficient context for an agent to know the full flow.

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 0%, and the description provides no information about the `manual` or `open_browser` parameters. It fails to compensate for the schema gap, leaving parameter meaning entirely to inference from names and defaults.

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 starts MYOB OAuth consent for a single business/company file. The phrase 'one business/company file' provides a scope qualifier that distinguishes it from the sibling myob_oauth_authorize, though it does not explicitly name the alternative.

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 instruction 'Repeat once per business' gives clear usage context, indicating this tool should be called per business, and likely multiple times for multiple businesses. It does not mention when not to use it or explicitly contrast with siblings, but the repetition guidance is a concrete usage directive.

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