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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false. The description adds two genuinely useful traits beyond that: the confirmation-safety gate and the fact that the asset is not 'live' until status is active. It remains cryptic about what is actually deleted/spent, whether the base64 payload has size/format limits, and failure 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?

Purpose is front-loaded and the safety workflow follows immediately, with little wasted text. The trailing fragment 'Fields: soclo://tools/soclo_ads_upload_ad_image' is a self-referential artifact that conveys nothing and should be cut.

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 10-parameter, destructive, nested-payload tool with no output schema, the description leaves major gaps: what imageBase64 accepts (formats, size), how accountId/platform/adAccountId relate, and what the caller receives back (an image ID for later use?). Only the confirm/status lifecycle is covered.

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 coverage is 60%, so the schema carries much of the burden. The description's param-related sentences (confirm:true after owner approval, 'same requestId') essentially restate the existing schema descriptions for confirm and requestId, and it says nothing about expectedCurrency, expectedBudgetType, expectedBudgetAmount, platform, or the nested payload structure.

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+resource+source format: 'Upload an ad image from base64'. This separates it from soclo_ads_upload_ad_video and soclo_ads_list_ad_images by media type. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 gating workflow ('preview, then owner-approved confirm:true with the same requestId') is useful context for when to set confirm. However, there is no guidance on when to choose this tool over list_ad_images (to reuse an existing asset) or get_ad_media, nor any stated prerequisites such as a valid adAccountId.

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