booking_login

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: visible browser, non-blocking return, background sign-in, user interaction, and post-call requirement. It also notes environment prerequisites. Could mention failure handling, but overall well-covered.

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 sentences efficiently cover purpose, behavior, and post-conditions without waste. Information is front-loaded, and every sentence adds distinct value.

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 interactive nature and single parameter, the description covers core behavior, environment requirements, and subsequent step. Slightly lacking in failure modes, but adequate for the complexity.

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 single parameter 'timeoutSeconds' is fully described with default (600), range (max 1800), and use case guidance (increase for slow SMS codes). Schema coverage is 100%, and the description adds meaningful context beyond the schema.

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 uses specific verbs ('start', 'opens', 'returns') and clearly states the tool initiates an interactive Booking.com login. It distinguishes itself from sibling tools, notably mentioning 'booking_login_status' as the follow-up call.

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 explains when to use the tool (to start login), that it runs non-blocking, and directs the agent to call booking_login_status after user completes sign-in. It also specifies requirements (Chrome, desktop display) and timeout tuning. No explicit 'when not to use' guidance, but the context is clear.

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