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

'Read only; no spend' restates readOnlyHint=true and destructiveHint=false already declared in annotations, adding no new behavioral information. It says nothing about pagination, result cardinality, or why the tool carries confirm/requestId parameters on an allegedly read-only call — a real ambiguity an agent would want resolved.

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?

Short and front-loaded, which is good, but the third sentence ('Fields: soclo://tools/soclo_ads_list_google_asset_groups') is an unexplained resource URI that consumes space without conveying usable guidance. Length is fine; the allocation of that length is not.

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 simple read-only list operation with no output schema, purpose plus read-only assurance is close to sufficient. The gaps are the campaign scoping requirement and why confirm/requestId appear on a read tool, but nothing blocks a correct invocation outright.

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 six parameters, a required nested `parameters.campaignId`, and only 50% schema description coverage, the description needs to compensate and does not — it never mentions campaignId or that results are scoped to one campaign. It also offers no clarification on the confirm/requestId/adAccountId/accountId distinction, which is the most confusing 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?

States a specific verb ('List') and resource ('Performance Max asset groups'), which cleanly separates it from the get_/create_/update_/remove_google_asset_group siblings. It does not explicitly name those siblings or state the scope limiter (campaignId), so it stops short of full differentiation.

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?

The only usage-adjacent statement is 'Read only; no spend', which asserts safety rather than telling the agent when to pick this over soclo_ads_get_google_asset_group or soclo_ads_list_campaign_assets. Nothing about prerequisites (a Google Ads account with PMax campaigns) or required campaignId scoping.

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