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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read only; no spend' largely restates structured data. It does add one useful inference for the agent — that the 'confirm'/spend-preview parameter in the schema is not required here — but omits return shape and scoping behavior for an openWorld tool.

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?

Two terse, front-loaded sentences with no filler. The 'Fields: soclo://tools/...' pointer is a reasonable documentation hook but is cryptic as written and occupies space that could have carried scoping information.

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?

Adequate for a simple read that is idempotent and needs no output schema, and the pointer to external field documentation helps. But with overlapping account-identifier parameters and no guidance on which platform/account combination to supply, an agent could still call this with the wrong scope.

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 with only 50% schema description coverage, and the description contributes zero parameter meaning. It does not explain the relationship or distinction between 'platform', 'adAccountId', and the required 'accountId', nor how the nested 'parameters' object is used — the exact gap the description should fill.

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 ('List custom conversion goals'), so the operation itself is unambiguous. However, it does not distinguish itself from close siblings such as soclo_ads_list_ad_conversion_goals, soclo_ads_get_campaign_conversion_goals, or soclo_ads_list_conversion_actions, which an agent must disambiguate on its own.

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' is a safety property, not usage guidance. The description never says when to pick this tool over the many other conversion-goal listing tools, nor what preconditions (e.g., which platform/advertiser scope) make it appropriate.

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