employer_ivf_coverageWhether a US employer's own benefit documents say it covers IVF or fertility treatment, with the dollar or cycle limit, who runs the benefit, and a verbatim quote and link to the document. Covers the large employers IVFcost.co has read; says so when an employer publishes nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| employer | Yes | The employer's name, for example Walmart or Google. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the read-only/idempotent annotations, the description discloses that coverage is based on the employer's own documents, what details are returned, and that it reports when an employer publishes nothing. It does not explain behavior for an employer that is entirely absent from IVFcost.co's coverage, which is a minor gap.
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 dense sentences, with the core purpose front-loaded and the coverage caveat immediately after. There is no filler, and every clause adds either output detail or scope.
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 one-parameter read-only lookup without an output schema, the description explains the return content and the main coverage limitation well. The one missing piece is explicit behavior when the employer is not in the dataset at all, as opposed to merely publishing no benefit document.
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 baseline is 3, but the description adds useful domain constraints: the employer must be a US employer and must be among the large employers IVFcost.co has read. It does not add input-format details beyond the schema's Walmart/Google examples.
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 states a specific verb and resource: whether a US employer's own benefit documents cover IVF or fertility treatment. It also lists the exact outputs (dollar/cycle limit, administrator, verbatim quote, link), which clearly separates it from sibling tools about clinic prices, grants, cost estimates, and general insurance rules.
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 scope implies when to use it: for a named US employer's own benefit documents, especially large employers IVFcost.co has read. However, it does not explicitly name alternatives or say when to prefer this over ivf_insurance_rules or estimate_ivf_cost.
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.