trello_get_member

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions that boards and profile information are included, but does not disclose rate limits, authentication requirements beyond parameters, error behaviors, or what 'profile information' entails. This is insufficient for a read tool with multiple optional parameters.

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, clear sentence that is well front-loaded with the core action and resource. Every word adds value, and there is no redundancy or fluff.

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 tool has 6 parameters and no output schema or annotations, the description is minimally sufficient but lacks details on return structure, behavior when memberId is 'me', and the relationship between parameters like 'boards' and 'organizations'. It provides a basic overview but leaves gaps.

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 the schema already documents each parameter. The description adds no additional meaning beyond the schema. For example, it does not explain the effect of different 'boards' enum values or how 'fields' filtering works. Baseline 3 is appropriate.

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 tool retrieves details about a specific Trello member, including boards and profile information. It uses the specific verb 'Get' and specifies the resource 'member/user', which distinguishes it from sibling tools like 'trello_get_board_members' (get members of a board) or 'list_boards'.

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 description implies use when needing member details but does not provide explicit guidance on when to use this tool versus alternatives like 'trello_get_user_boards' or 'trello_search'. No when-not or exclusion criteria are mentioned.

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