linkedin_invitations

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

No annotations exist, so the description carries the full burden. It reveals that accept/ignore/withdraw are mutations, but says nothing about whether they are irreversible, whether the 'confirm' flag gates them, whether authentication is required, or what the list actions return.

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?

A single compact sentence that front-loads the resource and then the capabilities. No waste, though a second clause spelling out the confirm/personName requirements would have earned its place.

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?

Three parameters, no annotations, and no output schema, yet the description explains neither the 'confirm' flag, nor the personName requirement for mutations, nor what the listing actions return. For a tool that mixes reads and destructive writes, this is under-specified.

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 only 33%: personName is documented in the schema itself, but the description adds no meaning for 'action' beyond restating the enum values in prose and says nothing about the undocumented 'confirm' boolean, whose required/optional role is left entirely opaque.

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 resource (pending invitations) and enumerates the supported verbs (list received/sent, accept, ignore, withdraw), so the agent can distinguish it from linkedin_connect, which sends new invitations. It is clear but does not explicitly name a sibling it must not be confused with.

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 implies the operational range by listing the five actions, but gives no guidance on when to pick this tool over linkedin_connect or linkedin_notifications, and no preconditions for the mutating actions. Nothing tells the agent when a given action is appropriate.

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