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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description still adds value by naming the fields the listing returns (price, duration, allotment, active member count, visibility) and by clarifying these are sellable products, not customer subscriptions. It stops short of mentioning pagination behavior, which the schema covers instead.

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 dense sentence front-loads the resource, its subtypes and its returned fields, followed by a short API endpoint reference. Zero filler; every clause 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?

With no output schema, the description usefully enumerates the returned fields, and the schema fully covers all 9 filter/pagination parameters. The only real gap is the absence of usage routing against the closely named sibling list_customer_memberships, which would matter for an agent choosing between the two.

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 every one of the 9 parameters is documented in the schema itself, including the expand/fields syntax and the for_sale, is_dropin and permits_registration_for_event filters. The description adds no parameter semantics beyond that, so the 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 ('List') and resource ('the membership products the business sells') and enumerates the subtypes — packs, recurring and prepaid plans — plus the fields returned. An agent can infer this is the product catalog rather than a customer's owned memberships, but the description never explicitly contrasts itself with goteamup_list_customer_memberships, so sibling differentiation is left implicit.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the obvious alternative (goteamup_list_customer_memberships) or of the filter conditions under which this tool is preferred. The agent must infer usage purely from the resource noun.

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