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

Annotations already declare openWorldHint, idempotentHint and destructiveHint, so the safety profile is covered externally. The description adds a real behavioral instruction ("Ask the user which ones"), indicating a confirmation step, but omits rate limits or irreversible side effects on LinkedIn. There is no contradiction with annotations.

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?

Three short sentences, front-loaded with the core action, with no padding. The parenthetical invitation_secret reference is the one sentence that damages rather than earns 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?

An output schema exists, so return values need no explanation, and annotations carry the idempotency/destructiveness profile. However, a mutation tool whose description identifies the wrong input field and never mentions the account scoping requirement is not fully complete for correct invocation.

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 the baseline would be 3, but the description names "invitation_secret" as the input while the actual required parameters are account_id and linkedin_id_or_url. This mismatch points the agent at a parameter that does not exist (and additionalProperties: false would reject it), actively misleading rather than adding meaning.

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 opening sentence names a specific verb and resource ("Accept a pending received connection request"), which clearly separates it from send_invitation and withdraw_invitation. It lacks explicit sibling naming (e.g. decline_invitation), so it falls 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 states when to use the tool and where the input originates ("invitation_secret from list_received_invitations"), which routes the agent correctly. It never states when not to use it or names decline_invitation as the alternative, so no exclusions are covered.

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