myob_account_list

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 only states 'List chart of accounts,' which implicitly suggests a read-only operation but does not explicitly confirm this, nor does it describe pagination, default business context, or any side effects. The behavior is left largely to inference.

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 an efficient single sentence with no filler words. It is front-loaded with the action, but it is minimalistic to the point of under-specification, lacking necessary parameter context without becoming bloated.

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 presence of three optional parameters and an output schema, the description is incomplete. It does not explain how to use business_id or filter, what the output contains, or how it relates to the broader MYOB authorization flow. The description is adequate only for a barebones list operation.

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?

The input schema has three parameters (top, filter, business_id) but the schema description coverage is 0%, and the description does not mention any of them. The parameter names give some hint, but the description adds no meaning to clarify their purpose, format, or defaults beyond what the bare schema provides.

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 action ('List') and the resource ('chart of accounts'), which distinguishes it from sibling list tools like tax_code_list and job_list. However, it is almost a restatement of the tool name and does not elaborate on what a chart of accounts includes, so it is clear but minimally informative.

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 provides no guidance on when to use this tool versus myob_account_get or other list tools, nor does it mention any context such as the need for a selected business or authorization. There are no usage alternatives, prerequisites, or exclusions mentioned.

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