portal_refillRequest a medication refill for the patient's current prescription. Creates a refill order that will be reviewed by a provider within 24-48 hours. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| patient_id | Yes | Patient ID | |
| bearer_token | No | Authentication token for the patient session |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds context beyond annotations: it states the action creates a refill order, requires authentication, and has a 24-48 hour review window. These details are not in the annotations and align with the readOnlyHint=false and destructiveHint=true flags, providing additional behavioral transparency without contradiction.
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 three concise sentences, front-loaded with the primary purpose, followed by the key behavioral outcome and authentication requirement. Every sentence provides distinct value with no redundant or filler content.
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 the simple parameter set (2 params, no enums, no nested objects) and the presence of an output schema, the description covers the essential aspects: purpose, creation of an order, provider review timing, and authentication. It is slightly incomplete regarding post-request actions or potential side effects, but these are either covered by annotations or the output schema.
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 description coverage is 100%, with both patient_id and bearer_token clearly documented. The description adds no extra parameter-specific meaning beyond saying authentication is required, which is already evident from the bearer_token schema. Baseline 3 is appropriate since the schema carries the full burden.
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 explicitly states 'Request a medication refill for the patient's current prescription,' which is a specific verb and resource, and further clarifies that it creates a refill order reviewed by a provider. This distinguishes it from sibling tools like medications_list or order_create.
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 clearly implies the context for use: when a patient needs a refill on an existing prescription. It also mentions the review timeline and authentication requirement, giving actionable context. However, it does not explicitly state alternatives or when not to use the tool.
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.
Most tools have distinct purposes with clear boundaries, such as auth_* for authentication, checkout_* for payment, and portal_* for patient portal actions. However, there is some overlap between checkout_status and auth_check_payment (both involve polling for payment status) and between portal_support and portal_message (both for communication), which could cause minor confusion.
Tool names follow a highly consistent verb_noun pattern throughout, with clear prefixes grouping related tools (e.g., auth_, checkout_, consent_, intake_, medications_, order_, portal_, provider_). This predictable structure makes it easy to understand the tool set's organization and purpose.
With 34 tools, the count is borderline high for a telehealth server, as it may feel heavy and complex for agents to navigate. While the tools cover a comprehensive workflow from authentication to patient portal, some consolidation (e.g., merging similar polling tools) could improve usability without losing functionality.
The tool set provides complete coverage for the telehealth domain, including authentication, eligibility checks, medication browsing, intake, consent, checkout, order management, and patient portal features. There are no obvious gaps; agents can handle the entire patient journey from start to ongoing care without dead ends.