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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description nonetheless adds real behavioral value: it enumerates the fields returned and frames the tool as a diagnostic for missing conversions. It does not mention pagination or result-size behavior, which keeps it short of a 5.

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 core action and scope are front-loaded in the first sentence, with the diagnostic purpose and the alternative tool after it. The parenthetical examples ('a page visit, an event, time on site') earn their place by defining what a conversion goal can be. No filler.

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?

There is no output schema, but the description compensates by enumerating the returned data (goal status, count type, value, tag tracking status). Combined with the full schema coverage on the only parameter and clear annotations, an agent has everything needed to call it correctly.

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 100% and the single accountId parameter is fully documented in the schema (including the conditional 'only needed when the sign-in can reach more than one account'). The description adds nothing about the parameter, so the baseline of 3 applies.

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 (List) and two named resources (conversion goals, UET tags), plus what each record contains (status, count type, value, tag tracking status). It is clearly separable from the write-side siblings (msads_create_conversion_goal, msads_set_conversion_goal_status) and from the reporting sibling it points at.

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?

Gives an explicit diagnostic use case ('use this to find out why conversions are missing') with the concrete signals to look for (paused goal, tag not recording), and routes numeric conversion reporting to msads_get_campaign_performance by name. Both when-to-use and where-to-go-instead are stated.

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