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

Annotations already declare destructiveHint=true, but the description adds substantial context beyond them: the withdrawal happens on LinkedIn itself, it cannot be undone, and it consumes a limited daily allowance (100/day). These are exactly the consequences an agent needs before a destructive call.

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-loads the id contract in a bracket, then the action, then the alternative and the rate limit. Dense but every clause earns its place; the bracket syntax is compact rather than wasteful.

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, the description explicitly states 'Ids out: none', covers irreversibility, the daily limit, and the bulk alternative. Nothing needed to invoke it correctly is missing.

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% (both params documented), so baseline is 3. The description adds provenance detail beyond the schema by giving the exact path ('pendingInvitations[].invitationId') and noting no ids are returned, which slightly exceeds the schema's own wording.

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 and resource ('take back ONE connection invitation you sent that is still unanswered') with clear scope. It explicitly distinguishes itself from the bulk sibling ('To take back many at once, withdraw_invitations') and from respond_to_invitation by requiring the invitation be unanswered.

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?

Names the exact precondition (a sent, still-unanswered invitation) and routes the agent to the alternative for bulk operations ('withdraw_invitations does that in the background'). The only usage decision an agent faces here is covered.

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