reminder_deleteDelete a reminder to your human.
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | Utility instance id from buy or list_utilities. | |
| reminder_id | Yes | reminder id (rem_...) from reminder_create or reminder_list. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "instance_id": "orm_exampleexampleexample2",
+ "reminder_id": "rem_exampleexampleexample2"
+ }
+]Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."Input schema / properties / passport_token / maxLengthAdded value: +200Input schema / properties / passport_token / patternRemoved value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing about permanence, whether a deleted reminder can be recovered, or error behavior for an unknown reminder_id — zero added behavioral context beyond annotations.
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?
It is a single short sentence with no waste, but brevity here reflects under-specification rather than economy — a destructive mutation tool warrants more front-loaded detail than one clause that merely echoes the title.
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 destructive, non-reversible mutation with no output schema, the description should clarify consequences and confirmation expectations. It conveys nothing an agent could not already infer from the name, title, and annotations, leaving the description functionally empty.
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 description coverage is 100%, so all three parameters (instance_id, reminder_id, passport_token) are fully documented in the schema itself, including their source fields. The description contributes no additional parameter semantics, which is the baseline expectation at this coverage level.
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 simply restates the tool name and title ('Delete a reminder to your human') without adding any specificity about what a 'reminder' is or how deletion differs from siblings like reminder_update, reminder_list, or reminder_create. It is effectively a tautology.
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?
There is no guidance on when to use this versus reminder_update (which might cancel or modify) or other delete siblings such as delete_ask, schedule_delete, or wakeup_cancel. No prerequisites or exclusions are stated.
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.