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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds only the 'no spend' reassurance, which is marginally beyond annotations. It says nothing about what a preview contains, whether rendering costs anything, or rate/pagination 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?

Sized well and front-loaded with the action, but the trailing 'Fields: soclo://tools/soclo_ads_get_ad_previews.' is an opaque artifact that conveys nothing actionable and consumes part of an already tiny description.

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?

A 6-parameter, nested-object tool with no output schema and a look-alike sibling 'generate_ad_previews' needs more: what a preview is (format/spec), which account param to use, and how the requestId/confirm flow applies to a read-only call. None of that 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?

Six parameters (two required, one nested object) at 50% schema coverage, yet the description adds zero meaning: no explanation of adId, formats, platform, accountId vs adAccountId, or the confirm/requestId review flow. The 'Fields: soclo://...' pointer is not a substitute for parameter semantics.

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 concrete verb+resource: 'Render previews of an existing ad'. However, it does not distinguish itself from the closely-named sibling soclo_ads_generate_ad_previews (or soclo_ad_pages_preview), so an agent could easily pick the wrong one.

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?

'Read only; no spend' gives a safety context but no when-to-use, no prerequisites (e.g. does the ad need to be approved/published?), and no guidance on which preview tool to choose over the near-identical sibling.

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