list_memberships

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'List' implies a read-only operation, but the description does not mention whether it returns all memberships or only the current organization's, any required permissions, or pagination behavior. This is a significant gap for a tool with no structured metadata.

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 sentence that is clear and free of filler. However, it is extremely sparse; while concise, it does not take advantage of the opportunity to add value in other dimensions. Still, for the dimension itself, it does not waste words.

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?

Despite the simplicity of the tool, the description lacks context about what a 'membership' refers to, whether it is scoped to the current organization, and the return shape. With no output schema and minimal description, the agent would likely need additional information to use the tool reliably.

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 includes two parameters (page and per_page), both with brief descriptions, giving 100% schema coverage. The tool description adds no additional parameter context, but per the baseline rule, with high schema coverage, this is acceptable at a score of 3.

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 'List organization memberships' uses a clear verb ('List') and a specific resource ('organization memberships'), which distinguishes it from sibling tools like get_membership (singular) and search_memberships. It is concise and unambiguous, though it could be slightly more explicit about scope (e.g., 'all' memberships).

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?

No guidance is provided on when to use this tool versus alternatives such as find_membership or search_memberships. There is no mention of filtering, pagination, or the typical use case, leaving the agent without context for choosing the right tool.

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