Get All Memberships

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

With no annotations, the description carries the full transparency burden; 'List all' indicates a read-only operation returning the full set with no filtering. It does not disclose pagination, authorization requirements, or behavior for an invalid boardId, leaving some uncertainty. Still, the core behavioral trait—retrieving, not mutating—is conveyed.

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 short sentence with no filler; 'List all memberships' is front-loaded, and 'on a board' adds the scoping needed. Every word earns its place.

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 only one required parameter and an output schema present, the one-sentence description plus the schema supplies enough for a confident call. It lacks explicit alternative guidance and deeper behavioral caveats, but the simplicity of the tool keeps the definition from feeling incomplete. Overall it is a solid, usable definition.

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%, so the description is the only source of semantic meaning for the single parameter. 'On a board' clarifies that boardId identifies the board whose memberships are listed. It does not specify boardId's format or constraints, but for a single string parameter named boardId this is adequate.

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 'List' with the resource 'all memberships' scoped to 'a board,' and the plural 'all' distinguishes it from the singular sibling get_membership. This makes the tool's purpose unambiguous even among many membership-related 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?

The phrase 'List all memberships' implies the tool is for retrieving the complete membership set for a board, which contrasts with the singular get_membership. However, it does not explicitly state when to prefer this over get_membership or get_users, nor mention any exclusions or filters. Usage context is implied rather than stated.

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