myob_inventory_item_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 disclosing behavioral traits. It only says 'List inventory items' and offers nothing about pagination behavior (e.g., the 'top' parameter), filtering semantics, business_id scoping, or the structure of the response. The lack of any behavioral detail leaves the agent without crucial operational information.

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, which is a plus. However, its brevity crosses into under-specification, as it omits essential parameter and usage context. It is a single, clear sentence but not appropriately sized for a tool with multiple parameters and no other documentation.

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 (top, filter, business_id), no annotations, no schema descriptions, and an output schema that is not explained, the description is grossly incomplete. It does not adequately prepare the agent to invoke the tool meaningfully, understand parameter effects, or interpret results.

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%, meaning the schema itself provides no explanatory text for any of the three parameters. The description does not compensate by explaining what 'top', 'filter', or 'business_id' mean or how they affect the listing. The agent is left to guess, which is a significant gap.

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 'List inventory items.' clearly states the verb 'List' and the resource 'inventory items', making the tool's primary function obvious. However, it does not distinguish this tool from siblings like 'myob_entity_list' or 'myob_inventory_item_prepare_create', so it only meets the bar for clarity without sibling differentiation.

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 alternatives. There is no mention of the intended use case, prerequisites, or scenarios where a different tool (e.g., 'myob_entity_list' or 'myob_inventory_item_prepare_create') might be more appropriate. This is a complete lack of usage guidance.

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