trello_get_board_members

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

With no annotations, the description carries the full burden. While 'Get' implies a read-only operation, it does not disclose return format, pagination, required permissions, or error behavior. The description adds no behavioral context beyond the verb itself.

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 with no redundant information. It front-loads the key action and resource, making it efficient and easy to parse.

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?

For a simple read-only tool, the description is adequate but minimal. It does not mention what fields the returned members will include, whether pagination is involved, or when to prefer this over sibling tools. Given no output schema, a bit more detail would improve completeness, but the tool's simplicity keeps it at a passable level.

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 coverage is 100% with descriptive text for all three parameters (apiKey, token, boardId), including the note that credentials are auto-provided. The description does not add additional parameter meaning, but the schema alone is sufficient, meriting the baseline score.

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 clearly states the action ('Get all members') and the target resource ('a specific Trello board'). It distinguishes from similar tools like trello_get_member (single member) and trello_get_user_boards (user's boards) by specifying that this tool returns all members with access to a given board.

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 trello_get_member or get_board_details. The description simply states the function without clarifying use cases, prerequisites, or exclusions.

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