get_contact_detailsPaid Business-plan tool. Provide an active Australian Manufacturing Directory Business API key to retrieve phone, email and street address. Subscribe at https://ausmanufacturingdirectory.com/membership.
| Name | Required | Description | Default |
|---|---|---|---|
| abn | Yes | Australian Business Number | |
| api_key | Yes | Active Business-plan API key |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the operation is a read-style retrieval of contact details and that API key validity is required. It does not mention failure modes, rate limits, or response format, but the core behavior is stated.
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?
Two compact sentences with no wasted wording. The key constraint ('Paid Business-plan tool') is front-loaded, and the subscription link is provided efficiently.
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 simple 2-parameter read tool with no output schema, the description covers purpose, prerequisites, subscription path, and the data returned. It is complete enough for an agent to invoke correctly, with minor gaps around expected response shape.
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 coverage is 100%, so the schema already documents both parameters ('abn' and 'api_key'). The description adds the 'active Business-plan API key' nuance and confirms the retrieved fields, but does not significantly expand parameter meaning beyond 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?
States a specific verb ('retrieve') and resource ('phone, email and street address'), clearly identifying the tool as a contact-details lookup. It does not explicitly name sibling tools, but the scope is distinct enough from get_manufacturer_profile and search_manufacturers.
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?
Clear prerequisite context is given: it is a paid Business-plan tool requiring an active API key, with a subscription link. It does not explicitly discuss when to choose this over the sibling tools, but no exclusion guidance is needed for such a focused lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are mostly distinct: listing categories, searching manufacturers, retrieving profiles, and getting contact details each have clear roles. There is some potential confusion between get_manufacturer_profile and get_contact_details since both relate to company information, but the descriptions clarify their boundaries.
All tools consistently follow verb_noun naming: get_contact_details, get_manufacturer_profile, list_categories, and search_manufacturers. The pattern is predictable and makes the tool purposes immediately understandable.
Four tools is well-scoped for a read-only directory lookup server. Each tool covers a necessary step: discovering categories, searching manufacturers, viewing a profile, and retrieving contact details as a paid add-on.
The core workflow of finding and inspecting Australian manufacturers is covered: browse categories, search by category/state, get a profile by ABN, and get contact details. There are minor potential gaps like searching by company name, but for the directory's stated purpose the surface is reasonably complete.