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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read only' is redundant repetition. The one genuinely additive phrase is 'no spend', but the description says nothing about pagination, result-set size, scoping to the account, or what the opaque 'Fields: soclo://tools/...' pointer is supposed to tell the caller.

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?

It is short and front-loads the core action, which is good. But the third sentence ('Fields: soclo://tools/...') is a cryptic internal URI that occupies real estate without conveying anything usable.

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 six-parameter list tool with a nested object and no output schema, the description omits the things an agent needs: whether results are scoped to accountId, whether platform filters the list, how audience types are returned, and any pagination behavior.

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% and the description adds zero parameter meaning. accountId (required) and platform have no schema description at all, and the description never clarifies the relationship between accountId and the separately described adAccountId, nor what the nested 'parameters.type' enum filters.

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 names a specific verb plus resource ('List custom audiences'), so the operation itself is unambiguous. It does not, however, distinguish this from close siblings such as soclo_ads_get_ad_audience or soclo_ads_list_ad_labels, leaving the agent to infer the plural/single boundary.

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 statement of when to call this versus soclo_ads_get_ad_audience or soclo_ads_create_ad_audience, nor any precondition or exclusion. The only usage-adjacent cue is 'Read only; no spend', which is a safety note rather than routing guidance.

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