getMemberships

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

With no annotations provided, the description bears the full burden of disclosure. 'List memberships' implies a read-only operation, but no behavioral traits are mentioned—such as whether it returns all memberships or requires authentication, pagination behavior, or sorting. This is minimally transparent.

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 extremely concise at two words, but this is under-specification rather than effective conciseness. It does not front-load key information or explain what the tool does in a helpful way, so the brevity is a detriment.

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 the complexity of the input schema (nested objects, multiple parameters) and the existence of sibling tools, the description is completely inadequate. It does not cover return values, required vs optional parameters, or the meaning of 'memberships' in context. The tool is underspecified.

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 0%, and the description does not explain any parameters. The input schema defines 'pathParams' (format, projectId) and 'queryParams' (offset, limit, nometa), but there is no textual explanation of their meaning or purpose. A description should compensate for low schema coverage, but it fails entirely.

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 is 'List memberships' which clearly states a list operation but is vague about scope. It does not specify whether memberships are for a project, user, or all memberships globally. Among siblings, there is also 'getMembership' (singular) and 'getMemberships' (plural), but the description does not differentiate between them.

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 like 'getMembership' (singular) or other list tools. The description does not mention any preconditions or context, leaving the agent to infer usage from the name alone.

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