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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so "Read only; no spend" adds almost nothing beyond them. The description also leaves unexplained the odd `confirm` parameter ("True only after owner approval of spending/deletion preview") on a supposedly read-only listing tool, and the "Fields: soclo://tools/..." pointer is opaque rather than informative.

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 text is short and front-loaded, but it wastes its limited budget on a repeated title (

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 tool with 6 parameters, a nested object, no output schema, and a confirmation-token pattern shared across the Soclo Ads surface, the definition should at minimum say what the listing returns and how `confirm`/`requestId` are used. None of that is present, leaving significant gaps.

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 description coverage means the description must compensate, and it does not mention any parameter. Nothing clarifies what `confirm`, `requestId`, `platform`, or the nested `parameters.adSetId` expect, so an agent gets no signal beyond the partially documented 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?

The description states a specific verb and resource ("List ad-group assets"), which is clearer than the bare name, but it is essentially a restatement of the title with no differentiation from close siblings such as soclo_ads_attach_ad_group_assets, soclo_ads_remove_ad_group_assets, soclo_ads_update_ad_group_assets, or soclo_ads_list_campaign_assets. An agent still has to infer scope from the name alone.

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?

There is no guidance on when to call this versus the attach/remove/update ad-group-asset siblings, and no prerequisite context (e.g., that an adSetId is required to enumerate its assets). "Read only; no spend" is a safety signal, not usage guidance.

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