convert_native_to_image

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

No annotations are provided, so the description must disclose side effects. It does not specify whether the conversion mutates the existing item, creates a new item, or deletes the original. Critical behavioral details (like reversibility or impact on the native ad) are missing.

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, front-loaded sentence with no filler words. It is appropriately sized for a simple one-parameter tool.

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 no output schema and minimal description, the tool lacks essential context about what the conversion does to the original, whether it returns something, and any prerequisites. The one-liner is not enough to fully understand the operation's consequences.

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?

The input schema describes the only parameter 'id' as 'Native ad item ID', achieving 100% schema coverage. The description itself adds no extra parameter context, so a baseline 3 is appropriate.

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 clearly states the action ('Convert') and the resource transformation ('a native ad item to an image ad item'). It is specific and distinguishes this from sibling tools that merely create/update/get/delete native or image ad items.

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?

The description implies usage when converting a native ad to an image ad, but does not explicitly state when to prefer this over creating a new image ad item or provide any exclusions or alternative guidance. The purpose itself gives a hint of the scenario.

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