ad_manager_li_search_targeting

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

Annotations declare readOnlyHint=true and idempotentHint=true, which the description does not contradict. However, the description adds no behavioral context beyond that—no mention of return format, scope, or limitations. For a tool with no output schema, this is a significant gap, and the description fails to disclose anything useful about its behavior.

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 concise in length but severely under-specified. It reads as a placeholder rather than a deliberate summary. There is no front-loading of key information, and it fails to convey the tool's purpose or usage, so it is not appropriately sized for the agent's 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?

With 4 parameters (1 required), no output schema, and no description of return values or expected behavior, the description is far from complete. An agent would have no idea what this tool does or how to call it effectively—only that it relates to search targeting in some unspecified way.

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%—each parameter has a terse description (e.g., 'Query parameter', 'Targeting facet'). The tool description itself adds no extra meaning. Per the baseline for high schema coverage, a score of 3 is appropriate, but the description could have explained how parameters interact or provided examples.

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 'Search targeting options' is a vague noun phrase. It does not state a clear action (e.g., 'search for targeting options') or the resource it operates on (LinkedIn ads). It provides no differentiation from sibling tools like ad_manager_fb_search_targeting or ad_manager_google_search_targeting, leaving the agent unable to distinguish this tool from its peers.

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?

There is no guidance on when to use this tool versus alternatives. No mention of platform-specific context, prerequisites, or typical use cases. The agent is left to guess based on the tool name alone.

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