get_cancellation_policyReturns the business's cancellation policy text. Use this when a user asks about cancellation terms, fees, or no-show policies. The response includes agent guidance on how to frame the policy with appropriate freshness caveats.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Business slug identifier |
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| has_policy | Yes | ||
| policy_text | Yes | ||
| guidance_for_agent | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / policy_text / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / policy_text / typeAdded value: +[
+ "string",
+ "null"
+]Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / slug / descriptionPrevious value: -"business slug"New value: +"Business slug identifier"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "guidance_for_agent": {
+ "type": "string"
+ },
+ "has_policy": {
+ "type": "boolean"
+ },
+ "policy_text": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "has_policy",
+ "policy_text",
+ "guidance_for_agent"
+ ],
+ "type": "object"
+}Input schema / additionalPropertiesAdded value: +falseInput schema / properties / slug / descriptionPrevious value: -"Business slug identifier"New value: +"business slug"Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "guidance_for_agent": {
- "type": "string"
- },
- "has_policy": {
- "type": "boolean"
- },
- "policy_text": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "slug": {
- "type": "string"
- }
- },
- "required": [
- "slug",
- "has_policy",
- "policy_text",
- "guidance_for_agent"
- ],
- "type": "object"
-}New value: +nullInput schema / additionalPropertiesRemoved value: -falseInput schema / properties / slug / descriptionPrevious value: -"business slug"New value: +"Business slug identifier"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "guidance_for_agent": {
+ "type": "string"
+ },
+ "has_policy": {
+ "type": "boolean"
+ },
+ "policy_text": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "has_policy",
+ "policy_text",
+ "guidance_for_agent"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing that the response includes agent guidance on framing the policy with freshness caveats, which is non-obvious behavioral context.
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 purpose followed by the usage trigger and a note on response content. Nothing is wasted or repetitive.
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?
The tool is simple (one required param), an output schema exists, and the description covers purpose, usage trigger, and response shape. Little remains that an agent would need before calling it, though it doesn't mention error behavior for an unknown slug.
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?
There is a single parameter (slug) with 100% schema description coverage, so the schema already documents it. The description says nothing about the slug, so baseline 3 applies.
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 opens with a specific verb and resource ('Returns the business's cancellation policy text'), which is unambiguous. It does not explicitly contrast with a sibling like cancel_booking, so it stops short of a 5.
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?
'Use this when a user asks about cancellation terms, fees, or no-show policies' gives concrete trigger conditions. It does not name alternatives or exclusions, which keeps it at 4 rather than 5.
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.