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

Annotations only declare that this is a non-read-only, non-destructive, open-world write. The description adds real operational context: a DRAFT creative does not run until activated via linkedin_update_creative_status, and validate_only performs a purely local check with no API call, returning would_create. It also discloses that creative_id comes from the response header and may be absent, with linkedin_list_creatives as the fallback.

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 purpose is front-loaded and each subsequent line carries distinct, non-redundant information rather than padding. It is dense and slightly sprawling with per-parameter lines, but no sentence could be dropped without losing a fact the agent needs.

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 5-parameter write tool with an output schema and annotations, the description covers sourcing the input, the lifecycle consequence of the default status, the dry-run mode, and the return-value caveat. Nothing an agent needs to call this correctly is missing.

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 0%, so the description has to carry all parameter meaning, and it does for four of five: post_urn format (urn:li:share / urn:li:ugcPost), status values and default, validate_only semantics, and workspace's optionality for single-workspace accounts. campaign_id, the other required parameter, is never explained (e.g. sourced from linkedin_list_campaigns), which leaves a small gap.

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 first sentence names a specific verb and resource: creating a creative from an existing LinkedIn page post inside a campaign. It is clearly distinguishable from sibling creation tools such as linkedin_create_campaign or linkedin_create_campaign_group, and even from a hypothetical dark-post creation path.

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 tells the agent exactly where to get post_urn (linkedin_list_page_posts, only posts with sponsorable=true) and explains why the dark-post route is not taken (w_organization_social is enabled but not yet requested). It also spells out the DRAFT-vs-ACTIVE consequence with a pointer to linkedin_update_creative_status.

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