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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the downstream dependency on bidding strategies, a genuinely useful behavioral note, but says nothing about pagination, scoping to a customer, or result shape beyond what annotations and the output schema provide.

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?

A single front-loaded sentence with no filler; the purpose leads and the use-case rationale follows immediately. Every clause earns its place.

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 simple list tool with an output schema (so return values need not be described) and full annotation coverage, the description supplies purpose plus the strategic context. The only real gap is the undocumented account_id/customer_id pair, which the description does not resolve.

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 0% for two parameters (account_id required, customer_id defaulting to empty), so the description carries the full burden and does not compensate. It only says 'in the account' and never explains the distinction between account_id and customer_id or how they interact, leaving the required parameter's semantics undocumented.

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?

Names a specific verb and resource ('Lists the conversion goals in the account'), scoped clearly to a Microsoft account. It distinguishes itself from the similarly named list_conversion_goals/list_custom_conversion_goals only through the tool name, not through the description text, so it falls short of full sibling differentiation.

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?

Explicitly states the context in which the result matters ('required for conversion-based bidding strategies (MaxConversions/TargetCpa)'), which tells an agent why and when to call it. It stops short of naming an alternative tool or an exclusion condition, so it is clear context rather than full when/when-not routing.

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