myob_list_invoices

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only mentions routing infrastructure (JWT, tenant, company scope) but omits critical behaviors like read-only nature, pagination, rate limits, or data freshness. The agent receives no insight into what happens during invocation.

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 very short (three sentences) and avoids fluff, but it is too brief to be useful. It front-loads the name and infrastructure details rather than actionable guidance.

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?

Despite the presence of an output schema, the description does not explain what the tool returns or how to interpret results. It lacks essential context for a listing tool, such as default sorting, filtering capabilities, or common use cases.

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 single parameter 'arguments' is a generic JSON string with 0% schema description coverage. The description says it is a 'JSON string of arguments for the connector operation,' which adds minimal meaning beyond the schema. It fails to specify what keys/values are expected inside the JSON.

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 states it is a 'connector operation list_invoices', which is essentially a tautology restating the name. It does not explain what invoices are being listed or provide any distinguishing features from sibling tools like myob_list_accounts.

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 on when to use this tool versus alternatives. There is no mention of filtering, scoping, or context where this tool is appropriate compared to other Myob list tools.

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