Get Member

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It conveys a read-only lookup via 'Get information' and hints at an authentication context with 'authenticated user,' but it does not mention required permissions, error behavior, or whether only public fields are returned. This is acceptable for a simple GET but not fully 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 two short, purposeful sentences with no filler or repetition of the title. The core lookup behavior and the 'me' convenience are front-loaded, making it easy for an agent to parse quickly.

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?

The tool is simple, with one fully documented parameter, so input side is complete. However, there is no output schema and the phrase 'information about a Trello member' is vague about what fields or shape the response will have, and it does not explicitly clarify that related resources like boards or organizations are excluded. Given the sibling set, a bit more scope clarification would make it complete.

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 schema already documents memberId with the same meaning: 'The ID or username of the member (use me for yourself).' Because schema description coverage is 100%, the description adds no meaningful parameter semantics beyond the schema, so the baseline score of 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 states a specific verb ('Get') and resource ('information about a Trello member'), and further narrows the operation by saying lookup is by 'ID or username' with 'me' as a self-reference. This clearly distinguishes it from sibling tools that fetch related resources like organizations, cards, boards, or search results.

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 only concrete usage guidance is 'Use me for the authenticated user,' which hints at a relevant scenario. However, the description does not explicitly say when to prefer this tool over search_members or the get_member_* sibling tools, nor does it provide any exclusion criteria. The right usage 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.