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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the data is read live through the connected account, and profile/post/company text is untrusted third-party data to be treated as data, never instructions — an important prompt-injection warning. It omits failure modes (private/missing profiles, rate limits), so 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?

Three sentences, front-loaded with the primary capability and the returned fields before the derived use cases. The competitor-spotting clause is slightly verbose with capitalized emphasis, but no sentence is filler.

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 return-value burden itself and does so thoroughly, listing every major returned field group including the company block. Combined with the trust warning and the connected-account sourcing, an agent has everything needed to call and interpret it.

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% with only two parameters, so the schema already explains that profileUrl accepts a LinkedIn URL or public identifier and that connectionId selects the sender. The description confirms the read happens through 'your connected account' but adds no format, validation, or default behavior beyond that, so the baseline of 3 applies.

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 and resource ('Get a rich profile card for ANY LinkedIn person by their profile URL') and enumerates exactly what comes back: name, headline, current company/role, location, about, recent posts, plus company industry/size/HQ. The capitalized 'ANY' implicitly separates it from the sibling get_my_profile, 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?

Gives concrete when-to-use context: research a prospect before writing a personalized message, and use the company description to identify and skip competitors. It does not name an alternative tool (e.g. enrich_profiles or search_people) or state when not to use it, so it stops short of full routing guidance.

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