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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. 'No spend' adds a small, useful reassurance for an ads-domain tool, but the description says nothing about pagination, result volume, or authorization requirements for the account, and the 'Fields:' URI fragment conveys no behavior.

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 purpose is front-loaded and the total length is short, which is good. But the trailing 'Fields: soclo://tools/soclo_ads_list_ad_conversion_goals.' is cryptic internal clutter that consumes space without telling the agent anything actionable.

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 six parameters, a nested object, no output schema, and two similarly named account identifiers, the description is far too thin. It does not explain what a 'conversion goal' record contains or how account-level listing relates to the many sibling goal tools.

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 description coverage is only 50%, and the description adds no parameter meaning at all. It does not clarify the distinction between the required 'accountId' and the sibling 'adAccountId', nor what 'platform' or the nested 'parameters' object control—precisely the ambiguity this description needs to resolve.

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 account conversion goals'), so an agent knows the operation immediately. However, it does not distinguish this from close siblings such as soclo_ads_list_custom_conversion_goals or soclo_ads_get_campaign_conversion_goals, which an agent could easily confuse it with.

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?

The description gives no when-to-use guidance, no prerequisites, and names no alternatives. 'Read only; no spend' is a safety reassurance rather than routing advice, leaving the agent to infer when account-level goals should be listed versus campaign-level or custom goals.

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