myob_bill_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 of disclosing behavior. It only states 'List purchase bills' without mentioning pagination limits, required authentication, output format, or any side effects. This is a significant gap for a tool that likely performs an API read.

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 brief (one sentence), which is concise in length but not appropriately sized for the information needed. It front-loads the core purpose but omits essential details, making it under-specified rather than efficiently compact.

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?

While an output schema exists, the description fails to explain the tool's behavior beyond a basic list operation. It lacks information about filtering, pagination, authorization requirements, or relationship to other bill-related tools. For a tool with three parameters and no annotations, this is insufficient contextual completeness.

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 does not compensate by explaining any of the three parameters (top, filter, business_id). The tool name and description give no clue about how these parameters affect the query, leaving the agent to guess their semantics.

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 ('purchase bills'), making the core purpose unambiguous. However, it does not explicitly differentiate itself from sibling tools like myob_bill_get or other list tools beyond the natural 'list vs. get' distinction, so it stops short of a full 5.

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 offers no guidance on when to use this tool versus alternatives. It does not mention that it is for retrieving multiple bills as opposed to a single bill via myob_bill_get, nor does it introduce the filter or pagination parameters. There is no exclusionary or alternative tool reference.

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