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

Adds substantial context beyond annotations: the exact refusal codes, the fact that a pending invitation blocks a resend, and the rate-limit ceiling with a 'do not retry today' instruction. It also documents the return fields (invited, member_urn, with_note, invitation_urn), which annotations alone don't convey. It stops short of saying whether an invitation can be withdrawn or how long the limit window lasts.

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?

Front-loads the core action, then the optional message, then the outcome/error semantics — a logical order. The result sentence is dense but every clause carries distinct information (return fields, two named refusal codes).

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, describing the returned fields and refusal codes fills a real gap, and the destructive/openWorld annotations cover safety. Minor gaps remain: no mention of how to recover from already_invited or whether the invite can be revoked, but otherwise complete for a 4-param write tool.

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 100%, so all four parameters are already documented, including the 300-character message limit that the description merely repeats. The description adds no meaning beyond the schema (no default/redundancy notes for from_account_id or in_workspace). Baseline 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 ('Send a connection invitation to a LinkedIn user'), which unambiguously separates it from siblings like linkedin_list_invitations_sent or linkedin_search. An agent can pick this tool without opening the 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 clear operational guidance for the failure modes ('an invitation already pending is refused as already_invited', 'rate_limited (do not retry today)'), which is actionable when-to/when-not. It does not explicitly name alternative tools for discovering the target, though member_urn sourcing is covered in the schema.

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