Get a Juggle booking with its applicants

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

Annotations only cover readOnlyHint and openWorldHint, but the description adds that the returned text is authored by third parties and is untrusted data rather than instructions — a genuine safety disclosure for a tool that returns free-form scraped content. It also surfaces actionable state the caller could not otherwise predict (whether you can cancel/edit/message, hours until an application expires), and notes the phone number exposed for booked sitters.

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 what the tool returns, then the id provenance, then the routing mappings, then the untrusted-data warning. The long field enumeration is dense but every listed item corresponds to a real payload field, so it earns its space; only the applicant/booked sitter parentheticals push toward over-stuffing.

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?

No output schema exists, so the description carries the full burden of describing the return value, and it does so field by field, including the payment total and breakdown and the permission flags. Combined with the id provenance and cross-tool id mappings, nothing an agent needs to call this correctly or interpret the result is missing.

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 description restates booking_id provenance, which the schema already documents, and says nothing about the 'view' enum (compact/full/raw), whose semantics live entirely in the schema description. It therefore adds little meaning beyond structured fields.

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 specific verb and resource ('Get one Juggle booking (sit/job) in detail') and then enumerates exactly what the payload contains: status, service, dates and times, kids/pets, address, applicants, booked sitters, payment breakdown and available actions. It is clearly the detail counterpart to juggle_list_bookings, so an agent can distinguish it from its siblings without reading 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?

Explicitly states where the required id comes from ('booking_id comes from juggle_list_bookings') and then routes downstream work to the right siblings: applicant accountIds feed accepting/declining, profileId opens juggle_get_sitter, userId is the sitter's messaging id. That is concrete when-to-use and alternative guidance, not implied context.

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