List your favorite Juggle sitters

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuine value by naming the returned fields and the two IDs needed for follow-on calls. It omits pagination, empty-list behavior and result limits, which are the remaining unknowns for a listing tool.

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?

Two sentences, zero filler: the resource is front-loaded and the downstream-ID guidance follows. Every clause carries actionable 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 carries the burden of describing returns and does so by listing the projected fields and key IDs for chaining, which is sufficient for a zero-required-param read tool. Only pagination and empty-state behavior are unaddressed.

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 single `view` enum parameter is documented in detail by the schema itself (compact/full/raw semantics). The description never mentions `view`, so it adds no meaning beyond the structured field — baseline 3 applies.

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 ("List the sitters you have marked as favorites") and enumerates the returned fields, which distinguishes it from the sibling juggle_list_sitters that returns all sitters. An agent can select between the two without opening either 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 tells the agent what to do next: use profileId with juggle_get_sitter and accountId for reviews, unfavoriting and booking invites, which implicitly routes to juggle_get_sitter and juggle_unfavorite_sitter. It does not state an explicit exclusion against juggle_list_sitters or when a favorite list is the wrong choice.

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