myob_contact_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the function name ('Get any contact') and does not explain the scope of 'any contact', required authorization, error conditions, side effects, or return format. This is a minimal repetition rather than a transparent disclosure.

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 with no filler, which is efficient. However, it is under-specified for a tool with two parameters and no annotations, bordering on too terse to be genuinely useful.

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 tool has no output schema and no annotations, so the description is the sole source of context. It fails to explain what constitutes a 'contact', how business_id affects the lookup, or what the agent should expect in the response. For a tool with this complexity, the description is not complete.

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%, so the description must compensate, but it only mentions 'by UID' without explaining the nature of the UID or the optional business_id parameter. No additional meaning is added beyond the schema titles; business_id is entirely ignored.

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 a clear action (get) and a specific resource (contact) with the key lookup parameter (UID). It differentiates from list tools (e.g., myob_customer_list) but does not explicitly distinguish it from the more generic myob_entity_get, which weakens sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives like myob_entity_get or the various list tools. It provides no context, exclusions, or complementary usage instructions, leaving the agent without decision support.

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