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

Annotations cover safety posture (readOnly=false, destructive=false, idempotent=false, openWorld=true), and the description adds real value beyond them: the shared_secret prerequisite differs by action (required for accept/decline, not needed for withdraw) and withdraw is described as cancelling a pending invitation. It omits irreversibility of accept/decline and any rate-limit or error behavior, keeping it short of a 5.

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 compact sentences, front-loaded with the prerequisite list tool and then branching cleanly by direction. Every clause carries operational information; only the generic 'Manage' opening is filler.

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?

For a mutation tool with no output schema, the definition supplies the prerequisite call, the per-action secret requirement, and the direction-to-action mapping. Minor gaps remain around failure modes (invalid/expired secret, wrong direction for an action) and return behavior, but an agent has enough to call it correctly.

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 the schema already documents all three parameters including the enum and the shared_secret requirement. The description restates this mapping rather than adding syntax, format, or edge-case meaning, so the baseline of 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?

The description names the resource (a LinkedIn connection request) and enumerates the exact operations per direction (accept/decline for received, withdraw for sent), which lets an agent distinguish it from siblings like linkedin_send_connection_request and linkedin_list_connection_requests. The only weakness is the generic lead verb 'Manage', but the body immediately disambiguates.

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 explicitly conditions each action on the request's direction and identifies linkedin_list_connection_requests as the source of both the request and the shared_secret. There is no explicit 'when not to use' statement (e.g., that other actions are impossible), but the routing is unambiguous.

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