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' merely restates structured metadata rather than adding to it. Nothing is said about result size, pagination, or why a read-only list carries a 'confirm' parameter intended for spending previews.

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 verb, which is good, but the third sentence, 'Fields: soclo://tools/soclo_ads_list_conversion_actions', is an opaque self-reference that conveys no usable information and occupies a third of the text.

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?

With 6 parameters, a nested object, no output schema, and roughly a dozen sibling 'list' tools in this namespace, the definition is far too thin — an agent cannot tell what accountId scopes, what 'platform' accepts, or what the confirm path means for a read.

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% across 6 parameters including a nested 'parameters' object and an unexplained 'platform', and the description mentions none of them. The presence of 'confirm' and 'requestId' on a read-only list is genuinely confusing and the description does nothing to clarify their role here.

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 conversion actions', so an agent immediately knows it is a read-only enumeration of conversion action entities. It does not, however, distinguish itself from nearby siblings like soclo_ads_list_ad_conversion_goals, soclo_ads_list_custom_conversion_goals, or soclo_ads_list_ad_conversion_goals, which names alone cannot disambiguate.

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' gives a safety context but never says when to prefer this over the conversion-goal listing siblings, nor when the required accountId scope applies. No exclusions, prerequisites, or alternative-selection guidance are provided despite many overlapping list tools.

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