linkfetch_linkedin_connection

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

With no annotations and no output schema, the description carries the full burden. It does disclose the meaningful states (connected / not connected / expired) and the recovery path via the connect link, which is good behavioral context. It stops short of describing auth prerequisites, the exact shape of the response, or what 'Cloud mode' implies, so it remains mid-tier for a tool with zero structured support.

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 core purpose and followed by the failure-path instruction; nothing is padded. The colloquial 'as whom' and the parenthetical fallback URL are slightly loose but not wasteful.

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 must carry the return-value semantics, and it does so only at a high level ('whether connected, as whom, and its state'). It never names the response fields, the connect-link field, or what 'Cloud mode' distinguishes, leaving an agent to inspect the raw response to act on 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no syntax, defaults, or formats need explaining.

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 clearly states this is a status-check tool that reports whether the LinkedIn account is connected, the identity behind it, and its state. It is trivially distinguishable from the data-fetching siblings (get_profile, search_jobs, etc.), none of which report connection status. It is phrased as a returned fact rather than an explicit verb+resource, which keeps it 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?

It gives an actionable branch for a negative result ('if not connected or expired, give the user the connect link'), which is useful handling guidance. However, it never says when an agent should call this tool (e.g., as a precondition before other LinkFetch calls), so usage is only implied rather than stated.

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