myob_supplier_list

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

No annotations are provided, so the description carries the full burden. It only says 'List suppliers' and does not disclose any behavioral traits such as read-only nature, pagination behavior, filtering options, authentication requirements, or rate limits. This is insufficient for the agent to understand side effects or constraints.

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 extremely concise with no wasted words, but it is so under-specified that it lacks the structure expected of a helpful description. It reads more like a label than a structured explanation, slightly above the 'Process' example but still not adequately organized.

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 has three parameters, no annotations, and no schema descriptions, the description is far from complete. It does not mention the business_id context, filter syntax, pagination limits, or what the output represents. Even with an output schema present, the description fails to provide the necessary operational context.

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 schema provides three parameters (top, filter, business_id) with types and defaults but no descriptions (0% schema coverage). The description does not compensate by explaining the meaning or usage of these parameters, leaving the agent without the necessary information to use them correctly.

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 ('suppliers'), which is a specific verb+resource pair. It distinguishes itself from sibling tools like 'myob_customer_list' by explicitly naming the suppliers resource.

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 usage is implied: use this tool when you need a list of suppliers. However, there is no explicit guidance on when to use it versus alternatives (e.g., myob_entity_list or myob_supplier_prepare_create), nor any mention of required context like an authorized business.

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