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

Annotations already indicate destructive=true and readOnly=false, which cover the side-effect profile. The description adds a few generic behavioral facts ('requires guest details...') but does not disclose additional consequences like charges, confirmation handling, or rate-specific guarantees. It is not contradicted by annotations, and the existing annotations lower the bar for this dimension.

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 compact: three lines that state purpose, prerequisite flow, and dependency sourcing. No filler or redundancy, and the key action is front-loaded first.

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?

With 9 parameters, an output schema, and annotations, the description covers the essential flow: linking get_hotel_rates and get_payment_methods. Optional parameters such as travel_profile_id and loyalty_account_id are documented in the schema, so the description does not need to repeat them. It is sufficient for an internal-flight booking action in this codebase.

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?

The schema descriptions cover 100% of parameters with strong contextual info (e.g. doc location from get_payment_methods). The description repeats that gondola_rate_id comes from get_hotel_rates and payment_id from get_payment_methods, which essentially restates the schema. It adds no new meaning beyond what the schema already provides, so the baseline of 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?

Directly says 'Book a hotel room', a specific verb and resource, and explicitly ties it to get_hotel_rates. This clearly distinguishes it from sibling book_vehicle and other tool names in the same group.

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?

Provides clear context for using the tool: it requires a rate from get_hotel_rates, guest details, and a saved payment method found via get_payment_methods. It does not explicitly mention when to avoid it or contrast with book_vehicle, but the prerequisite flow is well specified.

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