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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to cover safety. It adds useful behavioral context by describing the output: a risk level (low/medium/high/critical) and specific recommendations, plus the evaluation dimensions (profile, booking details, communication patterns). This goes beyond the annotations without contradicting them.

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?

Three concise, front-loaded sentences cover the purpose, outputs, and input guidance without redundancy. Every sentence contributes directly to operational understanding, making it highly efficient.

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?

The description adequately explains the tool's return behavior (risk level and recommendations) despite the absence of an output schema. It also lists relevant inputs and the decision context. It does not mention edge cases like missing data or computation method, but these are not essential for basic usage.

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 input schema describes all five parameters with 100% coverage, so the baseline is 3. The description adds minimal semantic value by listing parameter names and using 'and/or' to indicate optionality, but it does not clarify relationships or add detail beyond the existing schema descriptions.

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's purpose as a pre-booking guest risk assessment, specifying it evaluates guest profile, booking details, and communication patterns to produce a risk level and recommendations. This is a specific verb-resource combination, though it does not explicitly differentiate from the many sibling risk-assessment tools, such as assess_vacation_rental_booking_risk or analyze_guest_communication_risk.

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 provides clear context for when to use the tool: before booking, to help hosts decide whether to accept a request. It also indicates that multiple parameters can be passed, with 'and/or' implying flexibility. However, it does not explicitly state when not to use it or name alternatives, which would have distinguished it from overlapping sibling tools.

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