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

With no annotations, the description carries the full behavioral load and does most of it: it discloses state-dependent outcomes — no-op plus a message if already sent, a 'in the process of sending' report plus a recommendation to re-check list_scheduled, and that it prevents the item from ever reaching LinkedIn. Gaps remain around permissions, idempotency, and the error shape if the handle is stale.

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 state condition ('SCHEDULED but NOT sent') is front-loaded in the first sentence and the routing to the alternative follows immediately. The synonym list ('cancel invite, unschedule, pull back, stop sending, remove from queue') is somewhat padded and is the main thing that could be trimmed.

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?

For a single-parameter mutation with no annotations and no output schema, the description covers the trigger, the prerequisite lookup, the postcondition, and both edge cases. It does not describe what a success response contains or what happens if the handle is unknown or already cancelled twice, which keeps it from a 5.

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 0%, so the description must compensate, and it does: it identifies 'handle' as the draft_ handle obtained from list_scheduled or approve_draft, which the schema only names as 'handle'. It stops short of showing the literal prefix format or what happens with an invalid handle, keeping it below a 5.

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 ('Cancel a connection request (or message) that is SCHEDULED but has NOT been sent yet') with the scope explicitly narrowed by the queue state, which sharpens it well beyond the bare name. It also names the exact alternative (withdraw_connection_request) for the adjacent case, so the agent can distinguish it from siblings without opening a schema.

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?

Gives explicit trigger phrasing ('cancel / stop / don't send / take back'), tells the agent to locate the item with list_scheduled, and names the exclusion: if already sent, use withdraw_connection_request instead. When-to-use, prerequisites, and the alternative are all present.

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