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

Annotations only declare the safety profile (readOnly, idempotent, non-destructive); the description adds the operational traits an agent actually needs: nothing is charged, the customer flow on the page, the 7-minute time hold, the WhatsApp 6-digit verification, and the payment-responsibility boundary. This is substantive context beyond the structured hints.

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 purpose and the no-charge caveat are front-loaded, and each sentence carries distinct information. The customer-flow sentence is longer than strictly needed for tool selection, but it is relevant for an agent that must instruct the customer, so trimming would cost 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?

With no output schema, the description still says what is returned (a filled-in checkout link to hand to the customer) and who does the remaining steps. Combined with the schema-level parameter documentation and the annotations, an agent has everything needed to call it and act on the result.

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% and the enums/defaults (service, frequency) are documented in the schema itself, so the baseline of 3 applies. The description only alludes to 'the address and the visit' being pre-filled and does not add format or constraint detail 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?

Opens with a concrete verb and artifact: get a checkout link with address and visit pre-filled. It immediately bounds the action ('nothing is booked or charged by this tool'), which is exactly the distinction an agent needs from the sibling request_booking.

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?

Names the alternative (request_booking) and the precise condition that selects it: booking FOR the customer for home cleaning, confirmed by one tap on WhatsApp. It also states the agent-side rule ('never pay on the customer's behalf'), leaving no routing inference to the agent.

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