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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds a cost/rate disclosure ('Mindbody calls: 1') that an agent can use for budgeting, but says nothing about pagination, result volume, or default truncation behavior.

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?

It is short and front-loaded, but the final sentence 'Get the memberships at a site' largely restates the tool name and the route line, so one of three lines is redundant. The routing tip is well placed, yet the body is fragmentary rather than structured.

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 simple two-optional-parameter read tool with full schema coverage and rich annotations, most of what an agent needs is present. With no output schema, however, the description never hints at what a membership record contains or how results are shaped, leaving a gap it could have filled.

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 both parameters are fully documented in the schema, including the 'all IDs allowed by access level' default, so the description carries no parameter burden. It adds nothing beyond the schema ('at a site' merely echoes siteId), which is the baseline case.

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 ('Get the memberships') and even the underlying route (GET /site/memberships), and explicitly distinguishes itself from membership_summary. The only weakness is that the scope 'at a site' is bare-bones, but an agent can still tell this apart from its siblings.

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?

Provides a clear routing rule to the sibling membership_summary for the count-of-clients-per-membership question, which is genuine when-to-use-elsewhere guidance. It does not spell out when-not to use this tool or any prerequisites, so it falls short of a full 5.

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