get_manufacturer_profileRetrieve a non-contact company profile using an Australian Business Number. Phone, email and street address are available through the paid get_contact_details tool.
| Name | Required | Description | Default |
|---|---|---|---|
| abn | Yes | Australian Business Number |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the key behavioral trait that the profile is non-contact and uses 'retrieve' implying a read-only operation. However, it doesn't specify error handling, return format, or any side effects, which for a simple get is acceptable but not deep.
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, well-structured sentence that front-loads the purpose, immediately notes the non-contact nature, and then names the alternative. There is zero filler, making it highly efficient.
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 single-parameter retrieve with no output schema, the description provides sufficient context: what it returns (a non-contact profile), the required input (ABN), and where to get contact details. It could list specific profile fields, but that's not essential for correct invocation.
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 already documents the single parameter 'abn' with a description and pattern. The description repeats 'using an Australian Business Number' without adding any additional meaning or usage details beyond the schema, so it adds no value above the structured definition.
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 verb 'retrieve', the resource 'non-contact company profile', and the required input (ABN). It also distinguishes itself from get_contact_details by explicitly saying it is non-contact, making its purpose unambiguous.
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?
It explicitly points out that contact details (phone, email, street address) are available through the paid get_contact_details tool, giving a clear alternative and condition. This is a precise when-to-use-this versus when-to-use-that instruction.
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.