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

Annotations only mark the tool as non-read-only, non-idempotent, and non-destructive. The description adds crucial behavioral detail: the creative lands as pending_approval, is NOT published, and nothing reaches LinkedIn until approved. It also discloses required permission context (human or ads:write caller) and names the returned identifiers. This goes well beyond the structured 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?

Three focused sentences with no filler. The most important fact — that the creative is not published until approved — is front-loaded, and the return values are stated clearly. Every sentence earns its place.

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?

The description covers the output (adCreativeId and assetId) and the approval workflow, which is essential since there is no output schema. However, it does not clarify that only adCampaignId and name are required, nor what `name` should represent. It also doesn't mention content length limits or whether at least one content field is needed. Slightly incomplete for a 7-parameter creation tool.

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 only 29%, so the description needs to compensate. It adds meaning to headline, bodyText, and callToAction by describing them as text creative fields, and implies adCampaignId is the target campaign. However, the required `name` parameter is not explained, and the description lists content fields as if core while the schema marks them optional, creating mild ambiguity.

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 what the tool does: create a text creative (headline, body text, call to action) for an ad campaign. It distinguishes itself from sibling tools like campaignstack_approve_ad_creative by emphasizing the pending_approval lifecycle, and from campaignstack_create_ad_campaign by focusing on creative content rather than campaign setup.

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 gives clear contextual guidance: it is the creation step, and approval is explicitly routed to campaignstack_approve_ad_creative. This implies post-creation workflow. It stops short of explicit when-not-to-use or alternative tool comparisons, but the context is strong enough for an agent to understand the intended flow.

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