Cancel a prepared action

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

Annotations already declare openWorldHint=false and destructiveHint=false, and the description reinforces this by stressing 'local state only; performs NO external action' twice. It also adds state-machine detail (PENDING/CONFIRMED) that the annotations do not convey. No contradiction, and it contributes beyond the structured fields.

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 critical PREPARE/local-only caveat in brackets, then the operation and its usage in two short sentences. Every clause earns its place with no redundancy.

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 an output schema present, return values need no explanation, and the description covers purpose, effect, and usage. It is nearly complete for a one-parameter tool; the only gap is the unexplained actionId semantics.

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?

There is a single parameter (actionId) with 0% schema description coverage, so the description must compensate and largely does not. It only implies actionId refers to an action via 'PENDING or CONFIRMED action'; it never explains ID format, source, or the 8-64 char constraint.

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 (cancels) and a precisely scoped resource (a PENDING or CONFIRMED action), including the consequence ('can never be executed'). This clearly separates it from siblings like linkedin_get_action and linkedin_list_actions, which read rather than cancel.

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?

Explicitly gives the triggering context: 'Use when the user changes their mind or the draft is superseded.' That is clear when-to-use guidance, though it names no explicit alternative tool for related operations.

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