search_toolsList available 1Stay hotel booking tools. An optional keyword filters by search, book, cancel, or details; absence of a keyword returns all tools.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | No | Optional tool filter keyword, such as book, search, cancel, or details |
| Name | Required | Description | Default |
|---|---|---|---|
| tools | Yes | ||
| total | Yes |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseOutput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / total / maximumAdded value: +9007199254740991Output schema / properties / total / minimumAdded value: +-9007199254740991Input schema / $schemaPrevious value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseOutput schema / $schemaPrevious value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"Output schema / properties / total / maximumRemoved value: -9007199254740991Output schema / properties / total / minimumRemoved value: --9007199254740991Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseOutput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / total / maximumAdded value: +9007199254740991Output schema / properties / total / minimumAdded value: +-9007199254740991Input schema / properties / keyword / descriptionPrevious value: -"Keyword to filter tools (e.g. 'book', 'search', 'cancel'). Omit to list all tools."New value: +"Optional tool filter keyword, such as book, search, cancel, or details"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "tools": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "description": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "description"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "tools",
+ "total"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the behavior that absence of a keyword returns all tools, which is useful. However, it doesn't disclose details like whether the keyword is case-sensitive or whether it matches partial words, but that's minor given the simple nature of the tool.
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 with no waste. The purpose is front-loaded, and the optional keyword behavior is stated efficiently. Every sentence earns its place.
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 list/discovery tool with one optional parameter and an output schema, the description is complete. It explains the keyword filter and the default behavior. The only minor gap is not specifying the output format, but the output schema likely covers that, and the tool's simplicity reduces the need for more.
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 the schema already documents the keyword parameter. The description adds the behavior that absence of a keyword returns all tools, which complements the schema. Baseline 3 is appropriate because the schema does the heavy lifting and the description adds minimal extra meaning.
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 tool lists available 1Stay hotel booking tools and that an optional keyword filters by search, book, cancel, or details. It distinguishes itself from the sibling tools by being a discovery/meta-tool rather than a booking operation, though it doesn't explicitly name a sibling alternative.
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 explains when to use the tool: to list available tools, with an optional keyword to filter. It implies the alternative is browsing all tools without a keyword, but it doesn't explicitly state when not to use it or compare it to a specific sibling. The context is clear enough for an agent to decide.
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.