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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint), and the description adds substantial operational context beyond them: the ~20s LinkedIn re-sync latency, the daily caching rule when a prior re-sync found nothing, and the meaning of conversationCheck:'unverified'. These are real behavioral traits an agent cannot infer from structured fields.

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?

It is front-loaded with a clear opening clause, and most clauses carry genuine information. However, the entire definition is a single run-on sentence with deeply nested parentheses (the conversation/InMail clause), which impairs parsing and makes the informative caveats hard to extract on a quick read.

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 must describe returns, and it does list the output fields (connection, invite, conversation, reply ownership, recent posts, next action). Latency and edge-case semantics are covered, but the response format/shape and how to read each field's values remain somewhat implicit.

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%, so both parameters are already documented in the schema. The description only restates the required input ('Pass the person's profile URL') and says nothing about connectionId or which sender's relationship gets analyzed. Baseline 3 is correct when the schema carries the semantics.

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 ('analyze your relationship with ONE person') and enumerates exactly what it returns: connection status, pending invite, conversation/InMail, who owes a reply, recent posts, and a suggested next action. This makes it clearly distinguishable from siblings like get_conversation, get_linkedin_connection, or get_recent_posts, which each cover only a slice.

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?

Explicitly positions itself as 'the one call to make before writing a personalized message or deciding how to follow up,' which gives a clear usage trigger. It also names an alternative behavior (get_conversation with refresh:true) for forcing a re-sync, but does not state when NOT to use this tool or how it compares to composing the individual sibling calls.

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