ad_manager_li_create_integration

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

The description says 'Create', which is consistent with readOnlyHint=false and matches the annotations. It does not add any behavioral information beyond the annotations, such as whether the operation is idempotent (annotations say false) or any effects on existing integrations. No contradiction is present.

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 concise sentence, immediately clear and free of any unnecessary words. It is appropriately front-loaded and minimal.

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 is insufficient for an agent to understand what a LinkedIn integration is, what the creation entails, or what the result will be. It does not explain any preconditions, how it relates to other LinkedIn ad manager tools, or what a successful creation achieves.

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?

All parameters are described in the schema (100% coverage), so the schema already conveys their meaning. The description adds no additional semantics, relationships, or formatting details beyond what the schema provides.

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 the verb 'Create' and the resource 'LinkedIn integration', clearly distinguishing it from the Facebook and Google integration tools by naming the platform. This is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus the Facebook or Google integration creation tools, nor any prerequisites or context for when a LinkedIn integration is needed. The description offers no exclusions or alternatives.

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