Prepare LinkedIn Connection Acceptance

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

The description adds meaningful behavioral context beyond the annotations: it creates an 'immutable acceptance draft' and explicitly states that it does not accept the request. This clarifies side effects (no actual acceptance, no destructiveness) and complements the idempotentHint and destructiveHint annotations. 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?

The description is only two sentences and immediately states the core action ('Revalidate... and create...'), followed by a clear clarification. Every word earns its place; no fluff or repetition.

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?

The tool has an output schema, so return values are covered elsewhere. The description communicates the high-level purpose and non-acceptance behavior, which is sufficient for basic selection. However, the lack of parameter explanations and any mention of workflow sequencing (e.g., 'use this before accept.execute') leaves gaps for correct invocation, making it average.

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 0%, so the description must compensate. While it mentions 'member profile' and 'incoming-request controls', which loosely map to profile_slug and request_id, it does not explain context_id or explicitly describe what each parameter represents. The high-level phrasing does not give the agent enough guidance to correctly populate the three required parameters.

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 clearly states the tool's action: 'Revalidate the exact member profile's paired visible incoming-request controls and create an immutable acceptance draft.' It also explicitly differentiates from actual acceptance with 'This does not accept the request.' This makes it distinct from sibling tools like accept.execute and ignore.prepare.

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?

The description implies when to use the tool by stating what it does not do: 'This does not accept the request.' This signals that this is a preparation step and that a separate execute tool (e.g., accept.execute) is needed for actual acceptance. However, it does not explicitly name alternatives or provide specific 'use when' conditions, so it falls short of a full 5.

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