myob_sales_order_prepare_create

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

Without annotations, the description carries the full burden. It discloses the approval requirement, which is valuable, but doesn't explain whether this operation is read-only or creates a pending draft, what side effects occur, or how to proceed after preparation. The short two-sentence description leaves significant ambiguity about the tool's behavior.

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 sentences, no filler. Each sentence contributes: the first states the action, the second states the critical prerequisite (approval).

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?

Given the complexity (nested json_body, no annotations, no param docs), the description is insufficient. It doesn't explain the prepare/commit workflow, what the output schema contains, or how to construct a valid request. Users would need external knowledge to use this tool correctly.

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 parameter guidance. The parameters (layout, json_body, business_id) are entirely unexplained; json_body is a nested object with additionalProperties:true, making it especially important to document. The description fails to compensate for the lack of schema descriptions.

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's purpose: to prepare a sales order creation. It uses a specific verb ('prepare') and resource ('sales order'), distinguishing it from sibling tools like invoice_prepare_create or bill_prepare_create. The mention of approval adds context.

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 usage in a two-phase flow (prepare then approve/commit) but doesn't explicitly state when to use this tool vs alternatives like myob_entity_prepare_create or myob_raw_prepare_mutation. No exclusions or alternative recommendations are provided.

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