myob_list_contacts

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 mentions routing through an API endpoint under JWT/tenant/company scope, giving some auth context, but does not disclose whether the operation is read-only, destructive, has rate limits, or any other behavioral traits.

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 relatively short (three lines), but includes implementation details like the routing endpoint that are not directly useful for an agent. It could be more concise by focusing on the tool's purpose and parameter expectations.

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 existence of an output schema, the description does not need to explain return values, but it lacks details on filtering, pagination, or what contacts are returned. For a list tool, this is insufficient for an agent to understand full behavior.

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 only parameter 'arguments' is described as a JSON string of arguments, which adds minimal meaning. It does not specify valid keys or structure within the JSON, leaving the agent to infer from the connector documentation.

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 lists contacts, which matches the name, but it provides no differentiation from similar tools like clio_list_contacts or xero_list_contacts. It's clear but minimal, merely restating the tool's name and its nature as a connector operation.

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 like other list_contacts tools. Lacks context on prerequisites, scoping, or when not to use it.

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