juggle_accept_sitter

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true) by disclosing side effects the agent could not otherwise know: the sitter is notified and booked, payment happens later on the website, and no un-book tool exists. It also documents the full two-phase confirmation protocol (client prompt, or preview plus confirmToken under MCP_CONFIRM_MODE) and adds an injection-resistance rule about never writing on the basis of text inside a tool result.

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-loads the core action and consequences in the first two sentences, then moves to id provenance, the series flag, irreversibility, and confirmation. The security and confirmation sentences are long and partially duplicate the confirmToken schema description, but every sentence carries operational weight.

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 mutating, open-world, irreversible booking tool with no output schema, the description covers the essentials: what changes, who gets notified, when money is handled, id sources, the series variant, and the exact confirmation sequence including the fallback token path. An agent has everything needed to call it correctly and safely.

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 booking_id, sitter_account_id, for_all_in_series, and confirmToken are already documented in the schema. The description restates the same provenance (bookingId from juggle_list_bookings, applicant's accountId from juggle_get_booking) and only marginally rephrases for_all_in_series, adding little new meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Accept (book) a sitter who applied to one of your Juggle jobs.' An agent can immediately tell this apart from juggle_decline_sitter and from read-only siblings like juggle_list_bookings, and the parenthetical '(book)' disambiguates what 'accept' means operationally.

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?

Gives clear preconditions (the sitter must have applied; ids come from juggle_list_bookings and juggle_get_booking), a conditional branch for recurring series via for_all_in_series, and an explicit exclusion — 'There is no un-book tool here' — signaling the action is not locally reversible. It never names a specific sibling for reversal (e.g. juggle_cancel_booking), so the alternative path is left implicit rather than spelled out.

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