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

Beyond the annotations it discloses that the call sends no email and grants no access, that approval is required before any effect, that a request expires after 30 minutes, and how Free vs Pro seat limits cause refusals. The idempotency behavior is largely carried by the schema's idempotencyKey description (which the annotations' idempotentHint also signals), so the description's marginal contribution there is smaller, but the approval/expiry/plan-limit semantics are genuinely valuable and consistent with the 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?

Purpose and the critical constraint (no email, no access, approval required) are front-loaded in the first two sentences. The paragraph is dense and the plan-limit rules are elaborated at length, but nearly every clause carries actionable information; only minor tightening is possible.

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 still reports the key return values (approvalUrl, approvalId) and the follow-up tool, plus error classes (validation, plan_limit) and the untrusted-content warning. An agent can call this correctly and interpret the result without further context.

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 a baseline of 3 applies, but the description goes further by explaining that admin is not an accepted role and by spelling out the seat economics that make role choice matter (viewer is never refused for room on Pro; every role is refused on Free). This adds decision-relevant meaning on top of the enum values.

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 first sentence gives a specific verb (request invite), the resource (workspace membership), and the two available roles with their meaning (member can upload and share, viewer read only). It is immediately distinguishable from siblings like lnkdrp_add_contact or lnkdrp_create_share_link.

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 states prerequisites and alternatives: the admin role is not available here (invite admins in the app), approval must happen in a browser via approvalUrl, and lnkdrp_check_approval consumes the returned approvalId. It also names the exact conditions under which the request is refused (validation, plan_limit) rather than leaving them to inference.

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