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

No annotations are provided, so the description carries the full burden, and it does disclose two useful traits: no message is sent and no credits are consumed. It omits other behavior an agent needs, such as whether the referenced entity must already exist, permission/auth requirements, and whether the result is a single sample or a batch.

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?

Two short sentences, front-loaded with the action and immediately followed by the safety/cost constraints. No 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?

For a one-parameter preview tool with no output schema, the description covers intent and safety but leaves the meaning of the required id unresolved, which is the one thing an agent must get right to call it. Adequate but with a clear hole.

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 0% and the single parameter is a bare "id" with no description. The tool description says nothing about what that id identifies (agent, campaign, LinkedIn account, or lead), leaving the agent to guess — a genuine gap that the description could easily have closed.

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 (render a sample) and resource (first follow-up after connection acceptance), and the parenthetical scoping to the post-acceptance stage distinguishes it from preview_linkedin_invite without naming that sibling directly. Clear enough for an agent to pick between the two preview tools, though the differentiation is implicit rather than explicit.

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?

"No sending, no cost" implies a safe dry-run context and the parenthetical establishes it applies after a connection is accepted, giving implied usage. However, it never says when to prefer this over preview_linkedin_invite or other preview_* siblings, and no prerequisites are stated.

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