check_guest_risk_score

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Pre-booking risk assessment' doesn't reveal any behavioral traits—it doesn't indicate if this is a read-only operation, what permissions are required, how results are returned, or any rate limits. The description is too vague to inform the agent about how the tool behaves.

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 extremely concise with just two words, 'Pre-booking risk assessment', which is front-loaded and wastes no space. However, this conciseness comes at the cost of under-specification, but based on the dimension's focus on brevity and structure, it scores high.

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 complexity (involving risk assessment with no annotations or output schema), the description is incomplete. It doesn't cover what the tool does, how to use it, what parameters mean, or what to expect in return. With no structured data to rely on, the description fails to provide enough context for effective tool invocation.

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 has 1 parameter with 0% description coverage, meaning the schema provides no details about 'guest_email'. The description adds no parameter semantics—it doesn't explain what 'guest_email' is used for, its format, or any constraints. With low schema coverage and no compensation in the description, this leaves the parameter undocumented.

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 'Pre-booking risk assessment' restates the tool name 'check_guest_risk_score' in slightly different words, making it tautological. It doesn't specify what action is performed (e.g., 'assess' or 'calculate') or what resource is involved (e.g., 'guest' or 'booking'), and it fails to distinguish this tool from siblings like 'get_squatter_risk' or 'detect_extortion_pattern' that might also involve risk assessment.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing a booking context, nor does it differentiate from sibling tools such as 'check_availability' or 'create_booking' that might be used in similar workflows. There's no explicit or implied context for usage.

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