Search pharmacy items that do not need a prescription, available for delivery in Kenya. Prescription medicines are never returned here.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | medicine name, e.g. paracetamol |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility. It discloses that only non-prescription items are returned and that delivery is in Kenya. This is adequate for a simple search tool.
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 redundant words, front-loaded with the action. Every sentence adds value.
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 tool with one parameter and no output schema, the description is complete: it states what results to expect (non-prescription, Kenya) and the input format.
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% and the description adds no extra parameter information beyond the schema's 'medicine name' example. Baseline 3 is appropriate.
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 verb 'search' and the resource 'pharmacy items that do not need a prescription', with scope 'available for delivery in Kenya'. It distinguishes from sibling tools like find_doctor and find_groceries which are about different categories.
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 explicitly says to use this tool for non-prescription pharmacy items in Kenya, and states that prescription medicines are never returned. However, it does not provide explicit guidance on when to use alternatives like find_doctor or find_groceries.
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.
Each tool targets a distinct aspect: general info, doctor search, grocery search, medicine search, and onboarding. Their descriptions clearly differentiate them, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (about_mkliniki, find_doctor, find_groceries, find_medicine, join_mkliniki). No deviations.
With 5 tools, the server is well-scoped for its purpose of providing health and grocery services in Kenya. Each tool serves a clear function without unnecessary redundancy.
The toolset covers core functionalities: information, finding doctors, groceries, OTC medicine, and onboarding. Minor gaps like missing appointment booking or account management exist but are reasonable given the focused scope.