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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'Read only; no spend' merely restates structured data. The description adds no context about what is returned, permissions required, or error behavior when the asset group is missing — and the dangling 'Fields: soclo://tools/...' pointer conveys nothing actionable on its own.

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?

Very short and front-loaded with the core action, but the third fragment ('Fields: soclo://tools/...') is an unexplained URI that wastes space rather than earning it. Terseness here reads as under-specification rather than efficient writing.

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 6-parameter tool with a nested object, no output schema, and a confirm/requestId confirmation protocol in the schema, the description leaves critical gaps — especially since a 'confirm/owner approval of spending or deletion' pattern on a read-only getter is confusing and goes unaddressed. An agent cannot tell from the description what it will receive or when confirm applies.

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?

Six parameters at 50% schema coverage, with accountId, platform, campaignId, and assetGroupId carrying no schema descriptions, yet the description mentions none of them. Only the implicit notion that a specific asset group is identified can be inferred; nothing is added about the confirm/requestId confirmation flow that the schema hints at.

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: 'Get a Performance Max asset group', which is clear enough to distinguish it from create/update/remove siblings in the same family. It does not explicitly contrast with soclo_ads_list_google_asset_groups, though 'Get' (singular) implies single-item retrieval versus listing.

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?

No guidance on when to use this instead of soclo_ads_list_google_asset_groups or soclo_ads_get_ad_tree, and no stated prerequisites (e.g., needing a known campaignId/assetGroupId first). 'Read only; no spend' describes safety, not usage selection.

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