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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read only; no spend' merely restates structured data. Nothing is added about how the verdict is sourced or cached, whether it may be stale, or what values it can return — the aspects annotations cannot express.

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 is front-loaded in a short, efficient first sentence, but the trailing 'Fields: soclo://tools/soclo_ads_get_ad_review' is a dangling pointer that explains nothing and adds noise for an agent deciding how to call the tool.

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 verdict-reading tool with no output schema, the description never indicates what the verdict contains (approval statuses such as approved/rejected/pending) or whether the mutation-oriented fields confirm/requestId apply to this read. The unresolved 'soclo://' field reference leaves a key gap unfilled.

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 only 50%: confirm, requestId and adAccountId are described in the schema, but platform, accountId and the nested adId are undocumented. The description adds no parameter meaning at all — 'Fields: soclo://tools/soclo_ads_get_ad_review' is an opaque URI reference rather than field guidance, so it fails to compensate for the coverage gap.

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: 'Read the platform's review verdict for an ad', which is meaningfully distinct from soclo_ads_get_ad (ad data) and soclo_ads_list_ads. It never names a sibling to contrast with, so differentiation relies on the agent's own 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?

'Read only; no spend' describes safety, not when to call it. There is no indication of when this tool is preferred over soclo_ads_get_ad or soclo_ads_get_ad_previews, nor any prerequisite (e.g., use before activating an ad).

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