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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine access-scope disclosure beyond that: only approved/public/published data is returned and unlisted profiles are never exposed. It omits the failure mode for a non-public memberId, keeping it short of 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?

Two sentences, front-loaded with the action and returned resources, followed by the single most important constraint. No filler, nothing repeated from the annotations.

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 is the only signal about return content, and it only gestures at it ("public profile, public photo, published context") without indicating shape or what is omitted when a field is unavailable. For a single required-param read tool with strong annotations this is adequate but leaves real 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?

There is one parameter, memberId, with 0% schema description coverage, so the description carries the full burden and it mentions the parameter not at all. It does not say whether memberId is a chat member, network member, or global identifier, nor what happens on an unknown id.

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?

Uses a specific verb ("Read") and enumerates the exact resource set returned: public profile, public photo, published context. An agent knows what it gets. It stops short of naming which sibling (preview_profile, find_person_context) covers the adjacent case, so differentiation is implicit rather than explicit.

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 phrase "for display inside the person's current chat" implies the use case, and "never exposes an unlisted profile" hints at a boundary. But there is no explicit when-to-use versus preview_profile or find_person_context, and no statement of what happens when the profile is unlisted (error, empty, or fallback).

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