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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that: it discloses the guest-only perspective of the results, that the payload yields gift_id values usable for mutation, and warns that user-authored text is quoted content and never instructions. Return shape is only partially characterized, which keeps it out of the top band.

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?

Purpose and downstream usage are front-loaded in the first sentence, before the prompt-injection notice. The injection warning takes several lines, but it is load-bearing safety context rather than filler, so the length is defensible.

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 zero parameters, a read-only annotation and no output schema, the description supplies most of what an agent needs: what is listed, whose perspective it reflects, and which field to reuse next. Only the full returned structure is left implicit, a minor gap for a no-arg list tool.

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?

The tool takes no parameters, so per the rubric the baseline is 4. The description correctly adds nothing about inputs and instead points to the output field (gift_id) that feeds subsequent calls.

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?

The description gives a specific verb (list) and a precisely scoped resource: the user's own reservations/confirmations made as a guest on other people's lists, explicitly excluding their own lists. That negative scope cleanly separates it from reservation-creation siblings like reserve_gift and from list_invited_lists.

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?

It tells the agent when to reach for this tool by naming the downstream flow: take gift_id from the result into update_my_reservation or cancel_my_reservation. It does not explicitly contrast with siblings like list_invited_lists or list_gift_lists, so routing guidance is strong but not exhaustive.

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