create_inline_ad

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

Annotations already declare the write/destructive, non-idempotent, open-world profile, so the description needn't restate safety. It does add useful behavior — that ad content and creative are created atomically in a single call — but says nothing about what is returned (no output schema) or required permissions/ordering beyond media upload.

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 short sentences, front-loaded with the definition and mechanism, then the usage cue. Minor redundancy between "in a single call" and "from scratch," but nothing wasted.

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 12-parameter mutation with no output schema, the description covers what it does but omits the return value (e.g. created ad/creative ID) and any prerequisite ordering or account-scoping constraints. Adequate given the fully documented schema, but not complete for the tool's complexity.

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 every parameter (including the objective-conditional landingPageUrl and leadgenFormId requirements) is already documented in the schema. The description adds no format, default, or dependency detail beyond that, so the baseline of 3 applies.

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 and resource ("Creates a new LinkedIn ad with inline content") and clarifies the key mechanism: content and creative are built in one call without a pre-existing post. That implicitly differentiates it from the sibling create_creative, though it never names the alternative directly.

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?

"Use this to create sponsored content ads from scratch" gives an intended scenario but no explicit when-not-to-use rule or named alternative (e.g. "use create_creative instead if you already have a post"). Usage is implied rather than routed.

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