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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: 'Free; nothing is launched', the scope limitation that the map shows only provider-returned ISO countries and that cities/radius are unsupported, and that it reads instead of retrying.

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 purpose sentence is front-loaded and the scope/usage details follow logically with little waste. There is mild redundancy, since the card contents (budget, targeting) are described twice in adjacent sentences, but it reads efficiently overall.

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 read-only tool with rich annotations and no output schema, the description covers what the card shows (targeting, budget, currency, status), cost, and scope limits, which is nearly enough to call it correctly. The one gap is that the required campaign/account/platform parameters are never explained.

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 17%, so the description must compensate, and it largely does not. It adds meaning only for the countries concept ('proposed country display only', ISO-only, no cities/radius), while campaignId, accountId, platform, adId and adAccountId remain undocumented in both places.

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 specific verb (refreshes/reads back) and resource (country targeting map and launch card for an EXISTING campaign) and explicitly distinguishes it from the sibling soclo_campaign_chat_preview by contrasting the existing vs. preview card. An agent can tell what this does without opening the schema.

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 clear when-to-use guidance: 'Use it to read an activation back after an unknown outcome instead of retrying.' It also implies a relationship to soclo_campaign_chat_preview, but it doesn't explicitly state when not to use this in favor of preview/confirm, so it stops just short of full routing guidance.

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