List conversion API integrations per ad account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds only the GET endpoint path. It does not explain return shape, pagination, authentication needs, rate limits, or whether results are scoped to the current workspace or all ad accounts.

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 description is a single front-loaded sentence with no wasted wording. The endpoint parenthetical is compact and does not obscure the purpose.

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 no-parameter list tool with annotations and no output schema, the description is adequate but thin. It leaves unclear what is actually returned and how results are scoped, which matters for an open-world integration-listing operation.

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?

The tool has zero parameters, so there are no parameter semantics to clarify; the baseline is 4. The phrase 'per ad account' might suggest scoping, but there is no corresponding input parameter to document.

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?

The description states a specific verb and resource: list conversion API integrations per ad account, and includes the underlying GET endpoint. It is clear enough to distinguish this from mutation siblings such as conversions_setIntegration, though it does not explicitly name alternatives.

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?

There is no explicit when-to-use or when-not-to-use guidance. The name implies listing, but the description does not say how this differs from siblings like conversions_listDeliveries, conversions_requeue, or revenue_listIntegrations.

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