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

Adds substantial context beyond the annotations: no state change to the campaign, no LinkedIn-side action at call time, and a handoff token that only launch_campaign can redeem. The claim that it 'changes nothing' sits in mild tension with readOnlyHint=false, but the scope of 'nothing' is clearly campaign/LinkedIn state, not server bookkeeping, so this reads as nuance rather than contradiction. Token lifetime and any rate limits are left unspecified.

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 core fact (same preflight as launch_campaign, returns summary and token) and immediately dispels the side-effect assumption. The closing sentence on ZenMode's pacing engine is slightly tangential but supports the 'nothing happens now' message.

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 two-parameter tool with full schema coverage and no output schema, the description covers what comes back (summary and confirm_token), the non-mutating nature, and where the token is consumed. Remaining gaps, such as behavior on a non-paused campaign or token expiry, are minor but real.

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 100% and both parameters are documented there (campaign_id source, idempotency_key semantics), so the schema carries the load. The description adds flow meaning by introducing the confirm_token the next call needs, but says nothing specific about campaign_id or idempotency_key usage. Baseline 3 is appropriate.

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 (run preflight) on a specific resource (a paused campaign) and names the exact sibling it parallels (launch_campaign) and the one that performs the real action. An agent can distinguish this from launch_campaign and pause_campaign without opening any 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?

Makes the use case explicit: call this first for a paused campaign, then call launch_campaign with the returned confirm_token. It also preempts the most likely misuse by stating this call does not activate anything. It stops short of stating what to do when the campaign is not paused or when the token has gone stale.

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