myob_create_bill

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions routing and that arguments is a JSON string, but fails to state whether the tool is destructive, what side effects occur, authentication requirements, or how the connector operation behaves.

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 short but not concise; it is under-specified and omits essential details. The first sentence is redundant with the tool name, and the routing info is likely generic. Every sentence should earn its place, but here they fail to add substantive value.

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 tool's complexity (a create operation with a single JSON argument) and the existence of an output schema, the description still lacks critical context such as typical use cases, required fields, or behavior. It is incomplete for an agent to invoke 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 only repeats that the arguments parameter is a JSON string for the connector operation. It provides no detail on expected keys, constraints, examples, or required fields. This does not 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 merely restates the tool name ('Myob connector operation create_bill') and adds routing details, but does not explain what a bill is in MYOB or how this tool differs from similar sibling tools like xero_create_bill or billcom_create_bill. The purpose remains vague.

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?

No guidance is provided on when to use this tool versus alternatives, no prerequisites, context, or limitations are mentioned. The agent is left without any decision criteria.

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