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

With no annotations provided, the description carries the behavioral burden and does well by explicitly stating 'No sending, no credits,' which tells the agent this is a non-mutating, cost-free preview. It also notes the content is 'built from the campaign's agent,' giving useful context about how samples are generated.

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 a single, front-loaded sentence that lists the key outputs and immediately states the no-sending/no-credits constraint. There is no wasted text.

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?

With no output schema and no annotations, the description does a reasonable job naming the return contents and confirming no side effects. However, it leaves parameter semantics and any prerequisites or error conditions unaddressed, which are notable gaps for an agent invoking 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?

The schema has 0% description coverage for account_id and campaign_id, so the description must compensate. It only says 'for an account in a campaign,' which maps loosely to the two parameters but does not explain what kind of account ID is expected, whether the campaign must be active, or any other parameter semantics.

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 states a specific preview/sampling action and enumerates the returned artifacts: invite, follow-up, auto-reply, pitch, and signature for an account in a campaign. It is clear what the tool does, though it does not explicitly distinguish itself from sibling preview tools such as preview_campaign_linkedin_invite or preview_linkedin_followup.

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?

The description implies usage by saying it is for an account in a campaign and that it does no sending and consumes no credits. However, it does not explicitly say when to use this instead of the many related preview tools, nor does it name alternatives.

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