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

With no annotations, the description carries the full burden. It implies a read-only listing operation and discloses that the result contains a gift_id. However, it does not explicitly state there are no side effects, nor mention pagination, ordering, or permission requirements. The behavioral disclosure is adequate but not comprehensive.

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?

The description is two sentences with no wasted words. The first sentence states the core purpose and scope; the second explains how to use the result. It is front-loaded and concise.

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 zero-parameter list tool with no output schema, the description provides sufficient context: it explains what is listed, the scope, and that the result contains a gift_id for further actions. It does not describe the full result shape, but the key field is called out, which meets the needs of an agent.

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 zero parameters, so schema coverage is complete. The description adds no parameter details because none are needed. The baseline for zero parameters is 4, and the description meets it.

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 clearly states the tool's function: it lists the user's own reservations/confirmations on other people's lists (as invitee), explicitly excluding the user's own lists. This distinguishes it from list tools for one's own lists. The mention of using gift_id with update/cancel also clarifies its place in the workflow.

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?

The description provides clear usage context: it is for viewing reservations on others' lists, not one's own. It also gives actionable guidance by telling the agent to use the returned gift_id with update_my_reservation or cancel_my_reservation. However, it does not explicitly name a sibling tool as an alternative for one's own lists, though the exclusion implies it.

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