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

The description adds important behavioral context beyond the annotations: the message is actually sent, approval is mandatory, the URL is resolved against the campaign, and a connected Launchpad account is required. It doesn't go into repeated-send/error-result behaviors, but it does not contradict the annotations.

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?

The description is compact and front-loaded: it states the primary action, then the approval gate, then the technical dependency, then the prerequisite. Every sentence earns its place without unnecessary filler.

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?

This is a high-stakes, real-send tool; the description covers the mandatory approval step, the campaign membership constraint, how to choose the campaign, and how to connect the account. Combined with 100% schema parameter coverage, the agent has enough to decide when and how to invoke it.

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 input schema already documents campaign_id, linkedin_url, type, subject, and body meaning. The description adds context about reachability and preflight campaign resolution, but it does not substantially enrich individual parameter semantics beyond that baseline.

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 clearly states the action: sends a REAL LinkedIn message, InMail, or email via Zeekeo Launchpad to a profile in a campaign. This is a specific verb+resource pairing and is strongly differentiated from sibling tools by the Zeekeo workflow and explicit 'real message' emphasis.

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?

Provides explicit invocation rules: only after showing the drafted message and receiving explicit approval, use zeekeo_list_campaigns to select campaign_id, and confirm the recipient is reachable from that campaign. It also states the account connection prerequisite, making when-to-use very clear.

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