myob_metadata_get_tool_catalog

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

With no annotations, the description must carry the behavioral burden. 'Return' implies a safe read-only operation, and 'mutation policy' hints at important context, but it does not explicitly state that no changes are made, nor does it disclose any limitations or authentication requirements. The action is clearly read-only, so a 3 is appropriate.

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 directly states the purpose without any filler words. It is concise and well-structured, earning a 5.

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?

The description is sufficient for a simple zero-parameter metadata tool. It states the return value ('catalog of major MCP tools and mutation policy') and format ('machine-readable'). No output schema exists, but the description gives enough context for an agent to understand what to expect, making it complete for the tool's simplicity.

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 tool has zero parameters, and the input schema is an empty object. The description does not need to explain parameters; the baseline of 4 applies. It adds value by describing what the catalog contains (mutation policy), which is not evident from the schema.

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 'Return a machine-readable catalog of major MCP tools and mutation policy.' It specifies a distinct resource (catalog) and scope (major MCP tools and mutation policy), which differentiates it from siblings like myob_metadata_list_domains and myob_metadata_get_entity_schema.

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 usage for programmatic discovery of available tools and mutation policy, but it does not explicitly state when to prefer this over alternative metadata tools. No exclusions or alternative names are mentioned, though the context suggests this is the go-to for a high-level catalog.

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