Retrieve Hong Kong Foreign Domestic Helper statistics from Immigration Department data. Filter by year to analyze trends.
Statistics on Foreign Domestic Helpers in Hong Kong. Data source: Immigration Department
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Filter by specific year |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral details. It only states the topic and the data source ('Immigration Department'), without explaining what statistics are returned, how the year filter behaves, whether data is aggregated annually, or any limitations or update cadence.
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 compact sentence with no filler, and the data source is stated efficiently. It is appropriately front-loaded for a simple tool, though the brevity means some behavioral detail is sacrificed.
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 one optional parameter, full schema coverage, and an output schema present, the tool is relatively simple and the description provides some provenance ('Data source: Immigration Department'). However, it does not clarify what happens when no year is provided, which statistics are included, or how this tool fits alongside the sibling student visa statistics tool.
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 fully documents the single optional `year` parameter with a clear description and default null, so schema coverage is 100%. The description adds no additional meaning about how the year parameter affects the results, but the baseline of 3 is appropriate because the schema carries the semantic load.
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 identifies the resource ('Foreign Domestic Helpers in Hong Kong') and the operation type via the tool name and 'Statistics', so an agent can tell what domain it covers. It is not a tautology and names the data source, but it does not explicitly contrast with the student visa sibling tool or use a specific verb in the description.
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 implies use when the agent needs Hong Kong foreign domestic helper statistics, but it gives no explicit when-to-use/when-not-to-use guidance or alternatives. The presence of the sibling tool get_student_visa_statistics is not leveraged to help an agent choose between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.