get_hotel_details

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

Annotations already declare readOnlyHint and destructiveHint, so the description adds value by specifying what the tool returns (room options, pricing, cancellation policies, amenities). It aligns with annotations and provides useful context without redundancy.

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 with no wasted sentences. It starts with a clear purpose, flows into usage guidance, then details parameters and return value. Every sentence adds value and is appropriately front-loaded.

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 presence of an output schema, the description's summary of return content ('rooms, rates, policies, amenities') is sufficient. It also covers parameter semantics and usage flow. For a tool with 4 parameters and a well-defined output structure, this is complete.

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 0%, but the description compensates fully with an Args section that explains each parameter: hotel_id's source (Vervotech property ID from search_hotels), date formats (YYYY-MM-DD), and num_adults default. This adds critical meaning beyond the schema's bare types and titles.

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 verb 'Get' and the resource 'detailed information, room types, and rates for a specific hotel.' It distinguishes from siblings like search_hotels (which returns a list) and compare_rates (which compares multiple hotels), making its purpose unambiguous.

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 explicitly says 'Use this after search_hotels to get full details for a hotel the user is interested in.' This provides clear context for when to use it. However, it does not explicitly exclude alternative tools like get_hotel_reviews or compare_rates, leaving some room for improvement.

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