Retrieve total remittances received by Mexico in USD, broken down by yearly or quarterly periods. Choose yearly for annual totals or quarterly for periodic sums.
Total remittances received by Mexico per period, in USD. Use freq=quarterly for the quarterly series or freq=yearly for annual totals (the most recent year may be partial).
| Name | Required | Description | Default |
|---|---|---|---|
| freq | No | yearly |
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 carries the full burden. It adds the useful note that the most recent year may be partial, which is a behavioral trait. However, it does not disclose the return format (e.g., single value vs time series) or any other operational details. Minimal but not misleading.
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 sentences, no filler. The purpose is stated first, then usage guidance. Every word earns its place.
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 tool with one optional parameter and no output schema, the description covers the essential purpose, parameter semantics, and a data-quality caveat. It omits the exact return structure (e.g., whether it's a single number or a list), but given the simplicity, it is nearly complete. A minor gap.
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 schema has only one parameter 'freq' with enum values but no descriptions. The description explains what each enum value means (quarterly series vs annual totals) and adds the partial-year nuance, fully compensating for the 0% schema description 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?
The description clearly states the tool returns total remittances received by Mexico per period in USD. It names the specific resource (national totals) and differentiates from siblings like get_mexico_states (state-level) and get_us_states (US states).
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 tells when to use freq=quarterly vs yearly and notes the partial-year caveat. However, it does not explicitly say 'use this tool for national totals, not for states,' but the name and scope make that obvious. Slight lack of explicit alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.