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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: it runs validation checks before activating and returns the updated campaign status. It does not explain the downstream irreversible effect (launching outreach) that destructiveHint implies, which is the remaining gap.

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?

Three short sentences, front-loaded with what the tool does, followed by preconditions and the return value. No filler, no repetition of the title, and each sentence carries distinct information.

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?

There is no output schema, and the description compensates by stating that the updated campaign status is returned. Combined with the precondition list and full parameter coverage in the schema, an agent has what it needs to call this correctly; only failure behavior when validation rejects is unstated.

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 parameters are documented there, including the conditional requirement on linkedinConnectionId. The description only alludes to the LinkedIn account via its validation sentence and adds no syntax, format, or default information, so the schema is doing all the work.

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?

The description uses a specific verb pair and resource ("Start or resume a LinkedNav campaign"), which is far more informative than the title alone and naturally separates it from pause_campaign, create_campaign, and delete_campaign. However, it never explicitly contrasts itself with those siblings, so it lands at clear-but-undifferentiated rather than top-tier.

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?

It gives real context for invocation: use it to start or resume a campaign, and it discloses the preconditions that gate success (LinkedIn account, prospect/post count, subscription limits). There is no explicit when-not guidance or named alternative, which keeps it short of a 5.

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