myob_metadata_get_entity_schema

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

No annotations are provided, so the description must carry the full behavioral burden. It says 'Return', suggesting a read-only operation, but does not explicitly state that it has no side effects, require specific authorization, or mention error cases. The description adds little beyond what the tool name implies, leaving the agent without important behavioral context.

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 sentence, front-loaded with the main action. It is efficient but under-specified; it lacks necessary details about the entity parameter and the nature of 'write flow'. This is not concise in the value-added sense—it omits critical information that should be present.

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?

With no annotations, no output schema, and a sparse description, the tool is incomplete from an agent's perspective. There is no explanation of the return structure, no examples, and no mention of prerequisites like selecting a business. For a metadata utility, this missing context hinders correct invocation and use.

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 schema has one parameter 'entity' with zero description coverage, and the description only generically refers to 'for an entity'. It does not explain valid entity names, expected format, or examples, forcing the agent to guess what values are acceptable. The description fails to compensate for the lack of schema-level parameter 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 uses a clear verb ('Return') and identifies the resource ('known MYOB endpoint paths and write flow for an entity'). This distinguishes it from sibling metadata tools like list_domains and get_tool_catalog, which target different resources. However, 'write flow' is somewhat vague and could be interpreted in different ways.

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 provides no explicit guidance on when to use this tool versus alternatives. It only implies use for retrieving schema-related metadata, but does not mention contexts like preparation flows, authentication requirements, or when to prefer entity-specific getters. There is no reference to sibling tools or exclusions.

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