myob_inventory_item_prepare_create

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses one key behavior: approval is required before commit, which signals a staged, non-final operation. But it doesn't mention side effects, permissions, or what happens after approval, leaving significant ambiguity. This is more than minimal but insufficient for full transparency.

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 sentences, front-loaded with the core purpose and a critical constraint. It contains zero filler words, making it efficiently structured for quick parsing. The brevity is a strength, not a weakness, in terms of conciseness.

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 having an output schema, the description is incomplete for an operation with an open json_body and an approval workflow. It fails to explain the prepare-approve-commit sequence, how to use the approval tools, or what to pass in json_body. Given the complexity of the tool and the many sibling prepare tools, this is a significant gap.

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 information. The json_body parameter is an open object (additionalProperties: true) with no hints about required fields, and the description doesn't even mention that json_body should contain the inventory item details. The agent is left without any guidance beyond the schema's bare type declarations.

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 identifies the tool's purpose: 'Prepare inventory item creation' specifies the verb 'prepare' and the resource 'inventory item creation', distinguishing it from sibling prepare tools (e.g., customer, supplier). However, it doesn't elaborate on what 'prepare' entails beyond staging, so it's not as rich as a 5.

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 'Requires approval before commit' implies a two-phase workflow, giving some context about when this tool is appropriate (when approval is needed) and hinting that the operation is not final. However, it doesn't explicitly mention alternatives (like raw_prepare_mutation) or state exclusions (e.g., 'use this only for inventory items').

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