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

Annotations already flag destructive=true, non-idempotent, and open-world, so the safety bar is lower. The description adds genuine context beyond them: the operation is async, requires an owner-approved preview before confirm:true, expects requestId reuse for confirmation/recovery, and reports live only at active status. That is meaningful behavioral disclosure of the two-step approval flow.

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 core workflow sentences are tight and front-loaded, but the trailing 'Fields: soclo://tools/...' reference is unexplained and reads as a dangling pointer rather than actionable guidance, detracting from an otherwise compact definition.

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 destructive, non-idempotent async mutation with no output schema, the description covers the approval/preview and status lifecycle but omits how to poll for completion (e.g., via soclo_ads_operation_status) and what the payload fields control. Adequate but with clear gaps given the tool's complexity.

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%, but the heavy nested 'payload' object (level, fields, datePreset, filtering, breakdowns, timeIncrement, etc.) has no per-field descriptions, and the description only annotates the confirm/requestId workflow while deferring the rest to a cryptic 'Fields: soclo://...' pointer. For a 10-parameter tool with a large undocumented payload, this leaves real ambiguity.

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 a clear verb and resource ('Submit async insights report') and ties it to Soclo Ads. However, it does not distinguish this from clearly related siblings like soclo_ads_get_ad_insights_report and soclo_ads_query_ad_insights, leaving the agent to infer the async-submit vs. read distinction.

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?

It gives a useful workflow cue ('preview, then owner-approved confirm:true with the same requestId') and a state gate ('Claim live only when status is active'). But it never says when to choose this tool over the get/query insights siblings, so usage context is only implied.

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