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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description earns credit beyond them by disclosing the exact return payload scope and that a card image is included, which is displayable to the user — useful behavioral context an agent would not otherwise know.

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 core scope (one member's full profile) is front-loaded, followed by the field list and then the usage triggers. Four sentences with little waste, though the field enumeration is slightly dense and could be tightened.

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?

With no output schema, the description carries the burden of describing return contents and does so thoroughly, including the card image side effect. Annotations handle the safety profile. The only remaining gap is the unresolved identity of user_id.

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?

There is one parameter with 0% schema description coverage, so the schema does nothing to explain user_id. The description implies a specific member is being fetched but never states that user_id is the target member's identifier rather than the caller's — a real ambiguity given the sibling get_my_profile. It partially compensates but not fully.

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 opens with a specific verb and resource ('Return one member's full profile') and enumerates exactly what that profile contains (introductions, role/company, their own looking-for, industries, locations, university, connection status). This clearly separates it from list-style siblings like browse_directory or search_members, though it never names those siblings explicitly.

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?

It gives concrete trigger conditions ('when the user wants to know more about a person from a search before asking for an introduction or referral') plus verbatim user phrasings ('who is this', 'what can they help me with'). It lacks explicit when-not guidance or a named alternative (e.g., get_my_profile for the caller's own data).

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