check_stateSays whether Sunflower Clinic prescribes medication to residents of a US state, and lists the states it serves. Pass only the two-letter state code. Never pass a name, birthday or health details.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | Two-letter USPS code of the state the patient lives in, for example PA. Use DC for Washington, D.C. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations cover the safety profile (readOnlyHint), the description adds crucial behavioral constraints regarding acceptable input data (no PII/PHI). This is more useful than what structured fields provide alone.
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 definition is highly efficient, quickly stating the purpose and immediately following up with critical restrictions on input data with zero unnecessary phrasing.
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?
Given it is a simple read-only lookup with high schema coverage, the description provides all the necessary context for a reliable AI agent to invoke it 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?
Although the schema coverage is 100%, the description reinforces the semantic constraint that the parameter must be a two-letter code, which reinforces the 'pattern' provided in the schema description.
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 defines the tool's function: checking if the clinic serves a specific US state. This purpose is distinct from the financial or informational tools provided as siblings.
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 provides strong explicit usage guidelines by stating exactly what input to pass (two-letter state code) and, critically, what inputs to avoid (name, birthday, or health details).
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.