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

With no annotations, the description carries the full burden, and it delivers: it discloses the confirmation-email workflow, that no price is monitored until the traveller clicks the link, that unconfirmed bookings are deleted after 7 days, and that the user should expect the email. This is rich behavioral context beyond the schema.

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 front-loaded with the core purpose and then adds only high-value caveats: the confirmation link, the check_hotel_booking verification step, the 7-day deletion policy, and the existing-booking-only constraint. Every sentence earns its place without redundancy.

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 covers the essential workflow, timing, and verification path, and the schema fully documents the parameters. It doesn't describe the immediate return value or failure modes, but for a no-output-schema tool it provides enough context for an agent to invoke it and set user expectations correctly.

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 description coverage is 100%, so the baseline is 3. The schema already explains email delivery, country affecting rate source, and hotel-name matching; the tool description adds little parameter-level meaning beyond that. It therefore meets but does not exceed the baseline.

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 opens with a specific verb and resource: 'Enrol a hotel booking the traveller has ALREADY made into free price monitoring.' It clearly distinguishes this tool from the sibling check_hotel_booking by focusing on submission/enrolment rather than verification.

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 explicitly states when to use it: 'Use this only for a booking that already exists. It does not search for or make reservations.' It also tells the agent not to claim tracking is active until check_hotel_booking confirms it, which is precise, actionable guidance.

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