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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known; the description adds real value by disclosing the two-step approval gate, requestId reuse for confirmation/recovery, and the condition (status active) for a claim to go live. It does not say what happens without confirm:true or what the response contains, keeping it below 5.

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 in one clean clause and there is no padding, but the approval sentence is compressed into near-telegraphic fragments and the trailing "Fields: soclo://tools/..." URI conveys nothing actionable to an agent, so space is spent without adding meaning.

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, nested, six-parameter mutation with no output schema, the description covers the confirmation flow but omits the target-selection semantics (which entity types can hold the label, whether arrays are alternatives or additive) and any pointer to soclo_ads_operation_status for outcome recovery after "claim live only when status is active." An agent still has to guess at the core invocation shape.

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 description coverage is only 50%, and the description's two mentions (confirm:true, same requestId) merely restate the existing schema descriptions for those fields. It says nothing about the required nested target set (labelId plus adIds/adSetIds/keywordIds/campaignIds), nor about the accountId vs adAccountId distinction or platform — the gaps that actually cause misuse.

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 and resource ("Detach a Google Ads label") matching the title, so an agent knows the operation. However, the sibling set contains both soclo_ads_remove_ad_label and soclo_ads_update_ad_label / soclo_ads_attach_ad_label, and the description gives no signal for distinguishing detach from remove.

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 states a procedural requirement (preview, then owner-approved confirm:true with the same requestId, claim live only when status is active), which implies the call sequence. But it never says when to choose this over soclo_ads_remove_ad_label or how it differs from the inverse soclo_ads_attach_ad_label, leaving the primary selection ambiguity unresolved.

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