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. 'No spend' adds a small useful confirmation that no budget is consumed, but nothing about return shape or pagination is provided.

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?

Very short and front-loaded, but the trailing 'Fields: soclo://tools/soclo_ads_get_campaign_conversion_goals' is a low-value resource pointer that restates the tool name rather than adding usable 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?

No output schema and a nested 6-parameter input, yet the description says nothing about return values, the nested campaignId, or account selection. For a getter with this schema complexity it is underspecified.

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 explains none of them. The nested 'parameters.campaignId' requirement and the confirm/requestId semantics are undocumented in the description, which should compensate for the coverage gap.

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 ('Get campaign conversion goals'), which lets an agent distinguish it from related siblings like update_campaign_conversion_goals or list_custom_conversion_goals. It doesn't explicitly name an alternative, but the operation is unambiguous.

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 says nothing about when to select this tool versus the many conversion-goal siblings (list_ad_conversion_goals, list_custom_conversion_goals, update_campaign_conversion_goals). 'Read only; no spend' is context, not usage routing.

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