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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context by listing the data categories returned and the sub-action decomposition, but says nothing about pagination, ordering, or what happens to params for the help action. Adequate against a lower annotation-driven bar.

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 tight sentences: the first front-loads what data is returned, the second enumerates actions and the help affordance. Zero filler. It could be marginally sharper about the help mechanism, but the structure is sound.

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?

There is no output schema, so the description reasonably lists returned data categories and points to the help action for field discovery. However, for a multi-action tool with an opaque params object, it does not describe per-action inputs or return shapes, leaving the agent dependent on a discovery round-trip to call it correctly.

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 coverage is 50%, and the params object is free-form (additionalProperties: true), so the description must carry weight. It does meaningfully explain the help escape hatch for discovering action fields, which the schema only gestures at, but it never describes what any action's params actually contain. That partial compensation lands at the baseline.

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 names the resource and its contents (member profile, job search preferences, saved questions, photo) and enumerates the three read actions, so an agent can tell this is the read-side counterpart to update_profile. It lacks an explicit verb in the description body (the verb only appears in the title) and does not name the sibling it complements, so it falls just short of a 5.

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?

No when-to-use guidance is given. With siblings like update_profile, get_account, whoami and get_membership in scope, the description never says when to pick get_profile over those alternatives or when not to. The only procedural hint is 'Call with action help', which is a how-to, not usage routing.

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