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

Adds substantial context beyond the annotations: it returns immediately while the worker does single-session browser work, it never surfaces in li_job_result, it dedupes on a fixed id and deletes its own record (explaining why no jobId comes back), failed reads are errors never 'nobody replied', and untied threads are reported separately. Annotations only give the read/write/destructive/idempotent flags; this explains the actual mechanics.

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-loaded with the action and effect, then the rationale, then the consumer warnings. It is long, but nearly every sentence carries a distinct operational warning; only the parenthetical rationale could be tightened.

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 compensates fully: it explains that the call returns immediately, that no jobId is returned, that li_job_result will not contain it, and where the resulting changes must be read. Error and edge-case reporting are also covered.

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 100% and both optional filters (sessionId, sessionLabel) are already documented in the schema. The description implies a single-account sweep but adds no format or precedence detail beyond what the schema states, so the baseline 3 applies.

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 compound action: read the LinkedIn inbox, mark repliers, and cancel their remaining automated follow-ups. It explicitly positions itself against both a sibling (the scheduled sweep) and the follow-up reads (li_replies_to_answer, li_conversation_history), so an agent can place it precisely.

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 an explicit when-to-use case (on-demand counterpart to the hourly sweep) plus the failure modes it prevents: a reply noticed only seconds before the next scheduled send, and a finished-sequence replier never noticed at all. It also names the alternatives for reading results.

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