myob_entity_prepare_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explain what 'prepare create' actually does—whether it stages a mutation, validates a payload, or returns a transaction ID. The phrase 'using the endpoint registry' is cryptic and adds no clarity.

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 a single sentence, which is concise in length, but it is not well-structured or informative. It lacks any front-loading of key details, such as what the tool returns or how the endpoint registry works. The brevity does not compensate for the absence of useful content.

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 tool with five parameters, no annotations, and an output schema, the description is severely incomplete. It does not explain the prepare/commit workflow, how this tool fits into the entity creation process, or what the output schema represents. The agent is left without enough context to safely invoke this tool.

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 0%, and the description provides no parameter information. All five parameters (entity, layout, summary, json_body, business_id) are left unexplained, and the description fails to add any meaning beyond their names. 'layout' and 'summary' are particularly ambiguous in the context of a create operation.

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 'Prepare create for a supported entity using the endpoint registry' is vague and generic. It uses a tautological phrase ('prepare create') and does not specify which entities are supported or how this tool differs from the many sibling prepare_create tools. It fails to communicate the tool's specific role in the creation workflow.

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?

There is no guidance on when to use this tool versus the numerous specific prepare_create tools (e.g., myob_customer_prepare_create) or myob_entity_prepare_update. The description does not mention any workflow context, prerequisites, or alternatives, leaving the agent without direction.

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