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

Without relying on annotations, it discloses that execution is deferred and spread across the account activity window with human-like gaps, that the call returns immediately with a job_id and planned schedule, that the agent need not stay alive, and that the job self-pauses on quota exhaustion or disconnection and auto-resumes, with named webhook events. This is unusually rich behavioral context for a mutation tool.

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 core action and followed by scheduling, return, and safety context in a logical order, with every clause carrying information. It is dense and long-winded in places (repeated window/default phrasing), which keeps it from a 5.

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?

An output schema exists, so return values need not be detailed, yet the description still explains the job_id and planned schedule, the async lifecycle, pause/resume triggers, and webhook feedback. For a 9-parameter mutation tool this covers everything an agent needs to call it 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?

Schema description coverage is 100%, so the schema already documents window_start/window_end, timezone, days and items. The description reinforces the window defaults and quota constraint but adds no syntax or format detail beyond the schema, so the baseline of 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 verb and resource (queue a batch of LinkedIn actions) and enumerates the action types covered (messages, invitations, profile visits, comments). It also makes the asynchronous distinction from siblings explicit by naming send_message and connect as the loop-based alternatives it replaces.

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 threshold for use ('anything above a handful of actions instead of calling send_message or connect in a loop') and a required precondition ('Always show the user the items before queuing them'). The alternative tools are named, so selection between this and the single-action siblings is unambiguous.

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