remove_saved_resortRemove a resort from the signed-in user's saved list. Requires a SnowSure user access token (OAuth).
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Resort slug to remove |
| Name | Required | Description | Default |
|---|---|---|---|
| markdown | No | Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose). |
Changes observed during successful MCP inspections.
Output schema / properties / markdown / descriptionPrevious value: -"Human-readable markdown summary of the tool result."New value: +"Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose)."Output schema / requiredRemoved value: -[
- "markdown"
-]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the authentication requirement beyond annotations, which already indicate destructiveness and idempotency. However, it does not disclose behavior for invalid slugs or non-existent resorts.
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 concise sentences front-load the purpose and follow with a necessary prerequisite, with no extraneous information.
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 one-parameter delete operation with an output schema, the description covers purpose and auth. Slightly incomplete regarding error handling, but sufficient given the complexity.
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 input schema fully describes the parameter 'slug', and the description adds context that the resort slug refers to one in the user's saved list, providing marginal extra value beyond the 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 clearly states the action ('Remove a resort from the signed-in user's saved list') and distinguishes it from sibling tools like save_resort and list_saved_resorts by specifying the target is the user's own saved list.
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 mentions an authentication prerequisite ('requires a SnowSure user access token') but does not explicitly state when to use this tool versus alternatives or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.