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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds value by enumerating the specific data fields returned and the at-risk/bot-detection flags, which are behavioral outputs beyond the annotations. However, it does not disclose potential null fields, error conditions, or whether the profile is always fully populated, so it adds moderate but not rich behavioral context.

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?

Two sentences with zero filler. The first sentence front-loads the action, resource, and field list; the second sentence gives use cases. 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?

For a read-only single-resource lookup with two required parameters and no output schema, the description is nearly complete. It names the fields returned and the use cases. The only gap is that it does not clarify the meaning/format of the two parameters (especially projectId) or note any access prerequisites, but the annotations cover safety and idempotency, so the overall context is strong.

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 carries the burden for parameter meaning. The description does not explain what projectId or subscriberHash mean or how to obtain them, beyond the schema's pattern constraint on subscriberHash. It names the resource ('member') but not the identifier semantics. Baseline 3 is appropriate because the description adds some context (member profile) but leaves the two required parameters under-explained.

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 ('Load'), a specific resource ('one member's full profile'), and enumerates the exact fields returned (title, company, tags, clicked URLs, engagement percentile, at-risk state, bot detection). It also names two concrete use cases (pre-call briefs, enriching a shortlist). This clearly distinguishes it from sibling tools like sm_get_member_overview or sm_list_members.

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 gives explicit use cases ('Use for pre-call briefs and to enrich a shortlist'), which tells an agent when to invoke this tool. It does not explicitly state when NOT to use it or name alternative tools (e.g., sm_get_member_overview for a lighter profile, sm_list_members for bulk), so it falls just short of a 5.

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