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

Annotations already flag non-readonly, destructive, open-world. The description adds high-value context beyond them: it goes out immediately and cannot be unsent, the exact daily/weekly and note-based limits per account tier, and the specific error codes (note_limit_reached, linkedin_limit_reached). Minor gap: it doesn't describe response shape beyond the invitationId hint.

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-loaded with the core action and irreversibility, then limits and alternatives. The bracketed 'Ids in/out' header is terse jargon, and the limits paragraph is dense, but nearly every sentence carries actionable information.

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 and 4 params, the description compensates fully: it explains the return (invitationId), the withdrawal path, quota semantics, and failure modes. An agent has everything needed to call this correctly or choose an alternative.

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 is 3, but the description adds operational meaning beyond the schema's plain maxLength: the note-based 5-per-30-days free-account constraint and the conditional nature of email (only when LinkedIn requires it). The connectionId parameter is left unaddressed.

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+resource+scope: 'Send ONE LinkedIn connection invitation from your own account, now.' It clearly distinguishes itself from siblings like send_message, start_conversation, and campaign-based invites.

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?

Explicit when-to-use and alternatives: give the profile URL, optional note/email when LinkedIn requires it, use withdraw_invitation to take it back, use a campaign for many people, and get_usage to check remaining quota. Nothing is left to inference.

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