myob_metadata_list_domains

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

No annotations are provided, so the description carries the transparency burden. It adds scoping context ('supported by this MCP server') but does not disclose whether authentication is required, what the response format looks like, or any other behavioral details. The read-only nature is implied by 'List' but not made explicit.

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 a single, front-loaded sentence that communicates the tool's purpose with no wasted words. It is appropriately concise for a simple metadata listing tool.

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?

For a zero-parameter, simple listing tool, the description is mostly complete: it states what is listed and the scope. However, it could further note that the returned domains are used as input for other metadata tools like myob_metadata_get_entity_schema, which would improve integration 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 input schema is an empty object with zero parameters, so no parameter explanations are needed. The description's mention of 'entity domains' adds no additional parameter semantics beyond the schema, but the baseline for zero-parameter tools is 4.

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 tool lists MYOB entity domains supported by the MCP server. It uses a specific verb ('List') and resource ('MYOB entity domains'), and distinguishes itself from siblings like myob_metadata_get_entity_schema and myob_metadata_get_tool_catalog by focusing on domains.

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 implies this tool is used for discovering available domains, but it does not explicitly state when to use it versus alternatives, nor does it provide exclusions or references to sibling tools. Usage context is inferred from the tool's simplicity and name.

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