Prepare Ignoring a LinkedIn Connection Request

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

The description adds significant context beyond annotations: it reveals that the tool validates the current visible request, creates an immutable draft, and most importantly does NOT perform the ignore action. This is critical for an agent to avoid mistakenly believing the request is handled after this 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?

Two sentences, front-loaded with the action and the crucial negative statement. Every word contributes to understanding; no filler or repetition of schema details.

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 description effectively conveys the prepare/execute distinction and non-destructive nature, and the output schema likely covers return values. However, the lack of parameter semantics and the absence of an explicit pointer to ignore.execute leave gaps for an agent trying to invoke all required arguments correctly.

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?

With 0% schema description coverage, the description must explain parameter meanings. It hints at 'member profile' (likely profile_slug) and 'incoming connection request' (likely request_id), but does not map these explicitly, and context_id is entirely unexplained. The agent must rely on naming conventions and sibling patterns, which is unreliable.

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 uses specific verbs ('Revalidate', 'create') and clearly states the resource (incoming connection request) and the outcome (immutable ignore draft). It explicitly says 'This does not ignore the request,' distinguishing it from the sibling ignore.execute tool.

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 gives clear context that this is a preparation step, and the explicit 'This does not ignore the request' sets a when-not boundary. However, it does not explicitly name the corresponding execute tool or state the exact sequence (prepare then execute), 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.