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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds real context beyond that: spending/deletion requires an owner-approved confirm, and requestId must be reused for confirmation and outcome recovery. The clause 'Claim live only when status is active' is opaque and adds little.

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 sentences are dense, but the trailing 'Fields: soclo://tools/soclo_ads_update_ad_keyword' is a wasted pointer, and 'Claim live only when status is active' is an unclear fragment that consumes space without informing the caller.

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?

It covers the highest-risk element (the preview/confirm spending gate) for a destructive, open-world, 10-parameter tool with nested objects and no output schema. It is still incomplete on identifier parameters and the expected* reconciliation fields, so an agent could pass a partial payload without understanding the mismatch-rejection behavior.

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?

With 10 parameters and only 60% schema description coverage, the description clarifies the confirm/requestId contract and ties status=active to the keyword going live. It says nothing about keywordId/accountId/adAccountId or the expectedCurrency/expectedBudget*/adAccountId preview-verification fields, which are the least self-explanatory part of the schema.

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 names a specific action pair and resource: pause or enable a Search keyword. It separates cleanly from siblings such as soclo_ads_remove_ad_keyword (deletion) and soclo_ads_update_ad_set_status (different entity), but it does not explicitly say so, leaving that distinction to inference.

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 concrete prerequisite flow: preview first, then re-issue with confirm:true and the same requestId after owner approval. That is genuine when-and-how guidance. It stops short of naming an alternative tool or stating when-not to use it (e.g. bulk keyword changes).

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