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

Far exceeds the annotations: it discloses that confirm=false previews every item and flags problems while confirm=true creates real orders charged to the card on file, and notes that returns are evening-only with same-day turnovers depending on a second linen set. Those are exactly the consequences an agent needs before triggering a destructive, open-world write that carries destructiveHint=true and idempotentHint=false.

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?

Front-loaded with prerequisites and eligibility, then moves through item shape, confirm semantics, and the evening-return caveat in a tight sequence. Some sentences re-encode schema fields, but every sentence carries operational information rather than filler.

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?

For a destructive, open-world batch write with no output schema, the description covers the prerequisites, the preview-first safety path, the charging consequence, and what the preview response contains (per-item problems flagged). An agent has enough to call this correctly without guessing.

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 67%, so the schema already documents addressId, checkoutDate, nextCheckInDate default, notes, and confirm. The description restates the same semantics (confirm preview-vs-schedule, nextCheckInDate defaults to the day after checkout) and adds only the "up to 10" cap, which maxItems already encodes. Useful corroboration but little net-new meaning.

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: schedules linen pickups for several guest checkouts at once across the host's saved addresses, capped at 10. It names the sibling whose rules it shares (book_my_pickup) and the sibling that supplies addressId (get_my_account), so an agent can separate it from single-pickup booking tools without opening any schema.

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?

Explicit audience gate ("For short-term-rental hosts") and prerequisite ("Requires the connected Fold account"), plus the routing hint that addressId comes from get_my_account and behavior matches book_my_pickup. It lacks an explicit when-not clause (e.g. use book_my_pickup for a single property), but the multi-checkout framing makes the split reasonably clear.

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