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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description carries real weight by resolving the apparent tension in a 'booking' tool: 'Books and charges nothing by itself', then narrating exactly what the traveller does downstream (contact details, waiver, payment). It adds the 24-hour notice rule and the no-charge guarantee, which no annotation conveys.

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?

Four sentences, leading with the core action and link behaviour before preconditions and the confirmation requirement. Slightly dense in the middle sentence describing the checkout flow, but every sentence carries operational information.

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 explains what is produced (a link the traveller opens), what happens after, and where to source valid dates and pricing. An agent has everything needed to call this correctly and set traveller expectations, despite the mutation-sounding name.

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 coverage is 75% (guests has only min/max bounds), and the description compensates by framing guests as 'party size' and describing how tour, date and guests populate the checkout. It adds the price/date-validity context via get_tour, though it never echoes the 12-guest ceiling or pickup_hotel semantics beyond what the schema states.

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?

States a specific verb and resource ('Make a mapltours.com booking link for a tour or day package') and immediately distinguishes itself from start_transfer_booking by scoping to tours/day packages rather than transfers. An agent can route between the two booking tools without inspecting schemas.

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?

Explicitly names the prerequisite workflow: get_tour supplies the earliest date and exact price, and the agent must confirm tour, date, guests and price with the traveller first. The 24-hour notice constraint is stated up front, so both when-to-use and when-not-to-call conditions are covered.

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