list_my_reservationsView appointment slots you have booked, from the past week through the next 60 days. Use it to review upcoming reservations before cancelling one.
List the appointment slots you have booked, from the past week through the next 60 days. Read-only. Cancel one with cancel_reservation.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only/idempotent/non-destructive, so "Read-only" is partly redundant. However the description adds a genuinely useful behavioral trait: the returned time window (past week through +60 days). Pagination and ordering are not disclosed.
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 short sentences; scope is front-loaded and the sibling pointer is second. Nothing is wasted.
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?
Simple zero-parameter list tool with no output schema, and the description covers scope and the follow-up action. Ordering, result size, and item fields remain unspecified, which is a minor gap for an agent deciding whether one call suffices.
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 tool takes zero parameters, so the 4 baseline applies. The description correctly implies no filtering inputs are needed, though it doesn't note that the window is fixed and non-configurable.
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?
States a specific verb and resource ("List the appointment slots you have booked") and scopes it to past week through next 60 days, which separates it from reserve_appointment_slot and list_appointment_groups in the sibling set.
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?
Implies when to use it (viewing your own booked slots) and explicitly routes the cancel action to cancel_reservation. No explicit exclusion against list_calendar_events, but context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.