Generate a due diligence report for a Swiss company by UID, combining Zefix commercial register data, UID Webservice details, and optional SOGC publications.
Generate a due diligence report for a Swiss company using Zefix and UID Webservice data.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Company UID in format CHE-XXX.XXX.XXX | |
| includePublications | No | Include recent SOGC publications in report (default: true) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral load. It mentions external data sources (Zefix, UID Webservice) but omits whether the operation is read-only, what permissions are required, how long it takes, or what form the report takes (download, email, inline).
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?
A single sentence, front-loaded with the core action and resource. No filler or redundancy.
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?
No annotations and no output schema means the description should explain the report's contents and return behavior more fully. It gives only the data sources used, leaving the agent without essential context for invoking the tool correctly.
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 two parameters are fully documented in the schema. The description adds no additional syntax or default behavior beyond what the schema already provides, which is the baseline for high coverage.
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 ('Generate') and resource ('due diligence report') for a Swiss company using named data sources. It does not explicitly differentiate from siblings like get_company_details_uid, but the report-generation intent is distinct.
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?
No guidance on when to use this tool versus alternatives such as get_company_details_uid or search_companies. No prerequisites or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.