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

No annotations are provided, so the description must bear full weight. It does not disclose any behavioral traits like idempotency, authentication requirements, error handling, or rate limits. The description is purely content-focused, missing details about what happens when a hotel is not found or whether results are cached.

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 concisely convey the core purpose, output components, coverage scale, and language support. No filler or unnecessary repetition—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?

Despite lacking an output schema, the description adequately explains the review's structure (grade, suitability, six categories, verdict) and scoping (350 hotels, 19 languages). It does not cover return format or error responses, but for a content-retrieval tool, the description sets clear expectations.

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 coverage is 100%—all parameters are documented in the input schema. The description adds no additional meaning beyond noting the 19-language locale availability, which already exists in the enum. It does not clarify the format for 'hotel' or how 'city' narrowing works.

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 it provides an 'editorial review of a specific hotel' including a letter grade, suitability, and a six-category breakdown. This verb+resource structure is specific and distinguishes it from siblings like 'find_reviewed_hotels' or 'get_booking_advice' by focusing on a single hotel review.

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?

No explicit guidance on when to use this tool vs. alternatives is given. The description implies usage for obtaining a detailed editorial review, but does not mention exclusions or mention sibling tools such as 'find_reviewed_hotels' for checking coverage or 'get_city_calendar' for other needs.

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