Accept or ignore a pending LinkedIn connection invitation by specifying the sender's name and desired action.
Accept or ignore a pending incoming connection invitation.
Args: sender_name: Name of the person whose invitation to manage. action: Either 'accept' or 'ignore' (default: 'accept').
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | accept | |
| sender_name | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It explains the core actions and the default behavior, but it omits whether the action is reversible, what side effects occur after accepting or ignoring, and whether authentication or specific permissions are required.
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 compact and front-loaded, stating the action first and then the necessary parameters. Every sentence adds value with no filler or redundant repetition of the schema.
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?
The description is mostly sufficient for a simple two-parameter tool with an output schema, but it omits usage context and side-effect details. Given the absence of annotations, an agent would benefit from explicit notes on when to invoke this vs. related connection tools.
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 0%, so the description must compensate. It does clarify sender_name as the person whose invitation is managed and explicitly constrains action to 'accept' or 'ignore' with a default, adding meaning absent from the bare schema.
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 the tool accepts or ignores a pending incoming connection invitation. This specific verb-resource combination distinguishes it from sibling tools like send_connection_request and get_pending_invitations.
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?
No explicit guidance is given about when to use this tool versus alternatives. The description does not mention that it should be used after viewing pending invitations, nor does it note that it is not for sending or managing outgoing requests.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.