create_creative

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It clearly indicates a mutation ('Creates') and the reference-based nature, but it does not mention the default intended status, lead-gen dependencies, permissions, or what happens after creation. This adds little beyond what the schema already states.

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 sentence with the core action front-loaded. It is appropriately short, though the second clause is grammatically awkward and could be removed or rewritten for better clarity.

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 mutating tool with no annotations and no output schema. The description does not indicate return values, the default status behavior, or the lead-generation parameter dependenciescars. The schema fills in some gaps, but the overall definition is too thin for an agent to invoke it with full confidence.

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 parameter descriptions already carry the semantic load. The description only adds the 'post/share URN' hint and does not clarify conditional requirements like leadgenFormId; the 'or will be created' clause is potentially confusing rather than informative.

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 uses a specific verb ('Creates') and names the exact resource ('LinkedIn creative/ad under a campaign'), which distinguishes it from sibling tools like create_campaign and create_inline_ad. However, the phrase 'or will be created as a reference to existing content' is awkward and slightly obscures the clear statement of purpose.

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 provides placement context ('under a campaign') and a prerequisite ('Requires a content reference'), which implies the main use case of sponsoring existing LinkedIn content. However, it does not explicitly name alternatives such as create_inline_ad, nor does it state when this tool should NOT be used.

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