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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description is consistent with them (no contradiction). However, the description adds no behavioral context beyond the purpose: it does not disclose the batch capability (up to 50 URLs, visible only in the schema), the presence of irrelevant aliases like tweetId, or how invalid URLs are handled. The one-sentence description does not carry behavioral weight.

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 description is a single tight sentence with no filler, front-loading the verb and resource. It is efficient, though its brevity borders on under-specification. For a simple read action, the structure is appropriately minimal and well-ordered.

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?

Despite high schema coverage, the contextual picture is incomplete: there is no output schema, so the agent cannot anticipate the response shape; the batch capability (max 50 items) appears only inside the schema; and the mishmash of irrelevant aliases (tweetId, tweet_url, permalink) and ignored parameters (limit, offset, pageSize) could confuse an agent without upper-layer guidance. For a batch tool with 17 parameters and heavy sibling competition, one sentence is insufficient.

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 94%, so the schema carries the parameter-documentation burden: url is described as 'LinkedIn profile URL, vanity handle, @handle, or in/{handle} path', and aliases are marked 'Prefer url' while ignored flags are labeled. The description adds nothing beyond 'by URL', but the schema's thoroughness justifies the baseline 3.

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 uses a specific verb ('Get'), resource ('LinkedIn person profiles'), and input method ('by URL'), making the core action clear. However, it does not differentiate from sibling tools such as linkedin_live_profile_get_v2 or linkedin_live_person_resolve_v2; the 'batch' aspect implied by the name is not mentioned, so an agent cannot distinguish this from the single-get sibling based on the description alone.

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 provides no when-to-use guidance. With closely related siblings like linkedin_live_profile_get_v2, linkedin_live_people_search_v2, and linkedin_live_person_resolve_v2, an agent receives no signal about when to prefer the batch version over the single-get, search, or resolve alternatives. No exclusions or alternative conditions are stated.

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