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

readOnlyHint=true already establishes the safety profile, so the description's job is to add context — and it does, by spelling out the response composition (addresses, emails, phones, links, linked parent/child members, custom fields). That payload disclosure is genuinely useful given there is no output schema. It stops short of noting not-found behavior or auth requirements, hence not a 5.

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?

One front-loaded sentence giving the payload, followed by a compact endpoint mapping that helps tie the tool to the underlying API docs. Nothing is padded, though the endpoint reference is mildly redundant with the tool name.

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 one-parameter read tool with no output schema, the description covers what the caller needs: the resource, the identifier semantics, and the returned field groups. Missing only edge-case behavior (unknown id, permissions), which is minor at this complexity.

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% and there is a single integer member_id, so the schema already carries the parameter documentation (baseline 3). The description adds no format, range, or sourcing detail beyond what the schema states.

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?

States a specific verb (Fetch) plus the exact resource (one member) and enumerates the member varieties (organisation, contact, venue, user). The word 'one' implicitly distinguishes it from the sibling current_rms_list_members, so an agent can route correctly without opening either schema.

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?

Usage is implied by the GET /members/{id} reference and the single required member_id, which signals a direct lookup by identifier. But no explicit when-to-use framing, no mention of when to prefer the list endpoint instead, and no note about what happens when the id is unknown.

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