Get published weekly office hours and any source conflicts. These are not live appointment slots; confirm holidays and exceptions with the office.
| Name | Required | Description | Default |
|---|---|---|---|
| practice_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| hours | Yes | ||
| source | Yes | ||
| timezone | Yes | ||
| practice_id | Yes | ||
| practice_name | Yes | ||
| source_status | Yes | ||
| sources_checked | Yes | ||
| live_availability | Yes | ||
| information_may_be_outdated | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "hours": {
+ "type": "object"
+ },
+ "information_may_be_outdated": {
+ "type": "boolean"
+ },
+ "live_availability": {
+ "const": false
+ },
+ "practice_id": {
+ "type": "string"
+ },
+ "practice_name": {
+ "type": "string"
+ },
+ "source": {
+ "type": "string"
+ },
+ "source_status": {
+ "type": "string"
+ },
+ "sources_checked": {
+ "type": "string"
+ },
+ "timezone": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "sources_checked",
+ "information_may_be_outdated",
+ "source_status",
+ "practice_id",
+ "practice_name",
+ "hours",
+ "timezone",
+ "live_availability",
+ "source"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish this as a safe, idempotent read operation, so the description does not need to restate that. It adds useful behavioral context by noting that results are published data, may include source conflicts, and should not be treated as live appointment availability.
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, front-loaded with the core function and then the key caveat. There is no wasted text and the important distinction from live appointment slots is stated directly.
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 read tool with annotations and an output schema, the description supplies the necessary scope and caveats: published weekly hours, possible source conflicts, and holiday exceptions. Nothing critical is missing for correct invocation.
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 description does not explain the sole practice_id parameter, and the schema description coverage is 0%. Although the parameter has a single-value enum, the description itself adds no meaning beyond the structured schema.
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 uses a specific verb and resource: 'Get published weekly office hours and any source conflicts.' It also explicitly distinguishes this from live appointment slots, which helps separate it from siblings such as get_appointment_link.
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 clearly implies when to use the tool: retrieving published weekly office hours rather than booking or checking live availability. The exclusion of live appointment slots is useful, though it does not name a specific sibling alternative for appointment-related needs.
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.