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

Annotations already establish this is a safe read (readOnlyHint=true) with no external side effects (openWorldHint=false). The description adds real context beyond that: results are permission-filtered ('they can see') and include nested members' wishlists, so the agent expects an aggregate payload rather than a flat group list. Pagination or ordering behavior is still unstated.

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?

One sentence, front-loaded with the resource and scope, with no redundant restatement of the title or annotations. Every clause (group types, membership scope, visible wishlists) carries 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?

For a zero-parameter read tool with no output schema, the description adequately covers both scope and the shape of the returned content, including visibility filtering. What remains missing is minor: result ordering, pagination, and whether empty memberships return an empty list.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing any input options.

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?

A specific verb ('Lists') plus a specific resource ('wishlist groups and Secret Santa groups') with an explicit scope of 'the signed-in person belongs to'. It is clear without opening a schema, though it does not distinguish itself from nearby read tools such as list_my_wishlists or get_group_wishlist.

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?

Usage is implied through the 'my' framing — this is the entry point for the caller's own group memberships rather than one group's contents. There is no explicit statement about when to prefer a sibling tool or what to do if the person belongs to no groups.

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