getClientMemberships

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

There are no annotations, so the description carries the full burden. It only states 'active memberships,' implying a filter, but does not explain any other behavioral traits such as authentication requirements, pagination, data freshness, or what happens when no memberships exist. This is minimal disclosure.

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 a single, clear sentence with no wasted words. It is front-loaded and to the point, but its brevity leaves out important context that would improve usefulness.

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?

Given there are no annotations or output schema, the description is incomplete. It doesn't mention what the response contains, how it's sorted, or how it relates to other client endpoints. The description is adequate for a simple read but lacks enough context for an agent to fully anticipate behavior.

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 input schema covers both parameters with basic descriptions, so the baseline is 3. The tool description adds no additional meaning beyond the schema; it doesn't explain how the parameters affect the result or how locationId filters memberships.

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 uses the specific verb 'Get' and identifies the resource as 'client's active memberships.' It clearly indicates the tool returns a client's memberships, but it does not explicitly distinguish it from sibling tools like getClientContracts or getClientAccountBalances, so it doesn't quite earn a 5.

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 no guidance on when to use this tool versus alternatives such as getClientContracts or getClientAccountBalances. There is no mention of prerequisites, typical use cases, or exclusions, so it scores low.

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