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

readOnlyHint=true already establishes this as a safe read. The description adds useful context about the record shape and the notion of a platform-calculated status, but says nothing about pagination behavior (despite cursor params), result volume, or rate limits, so it only modestly exceeds what the annotations provide.

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?

Two short sentences: the first front-loads purpose and payload, the second pins the underlying endpoint. No filler or redundancy.

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 fields returned, which is the main thing structured data does not cover. Combined with fully documented parameters, an agent has enough to call it correctly, though sibling disambiguation remains missing.

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%, so every one of the 9 parameters is already documented in the schema. The description echoes a few of the returned/queried concepts (plan, price, discount, start/end dates, status) without adding format or filtering semantics, so 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 (memberships), and even disambiguates the domain term with a parenthetical — 'recurring plans sold to members/companies' — plus the fields the record carries. It does not differentiate itself from the closest sibling, officernd_list_contracts, so an agent must still infer which list endpoint covers which concept.

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 guidance on when to use this tool versus officernd_list_contracts, officernd_list_members, or officernd_list_payments, and no stated prerequisites or exclusions. The only usage signal is the implied 'list' behavior, leaving routing decisions to the agent.

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