get_similar_hotels

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. Description does not add significant behavioral context beyond stating it returns a list. It is consistent with annotations, but the bar is lower due to annotations covering safety profile.

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?

The description is concise and well-structured: one-line purpose, usage guidance, then args and returns. Every sentence serves a purpose with no extraneous text.

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?

Given the tool's simplicity and presence of an output schema (mentioned in context), the description covers the key aspects: purpose, usage, parameters, and return type. No major gaps.

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 descriptions are absent (0% coverage). The description provides brief but helpful explanations for each parameter, e.g., 'The hotel's Vervotech property ID (from search results)' and 'Check-in date in YYYY-MM-DD format.' This adds value but is minimal.

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 title 'Get similar hotels' and first sentence 'Find hotels similar to one the user is looking at' clearly state the verb and resource. It distinguishes from siblings like search_hotels, get_hotel_details, and compare_rates.

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?

Explicitly says 'Use this when a user wants alternatives, comparisons, or asks show me hotels like this one.' Provides clear context but does not mention when not to use or alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.