pinterest_get_conversion_setup

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

With no annotations available, the description carries the full disclosure burden and does state a crucial behavioral guarantee: 'This never sends or deletes conversion events.' It stops short of covering pagination, rate limits, or authentication requirements, but the most important side-effect profile (read-only) is explicit.

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?

Two tightly scoped sentences front-load the purpose and then add the key safety qualifier. No filler or repetition of schema details appears.

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 eight parameters, no output schema, and no annotations, the description is too high-level: it omits parameter semantics, default behavior, return shape, and pagination. The purpose is clear, but an agent cannot fully infer how to use the optional filters or interpret the result.

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%, and the description only indirectly clarifies the surfaces parameter by listing the same category names; the other seven parameters (adAccountId, lookbackPeriod, sourcePlatform, ingestionSource, includeDeletedTags, pageSize, bookmark) receive no semantic explanation. The description does not compensate for the absence of schema descriptions.

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 uses a specific verb ('Inspect') with a clear resource ('Pinterest conversion measurement configuration') and enumerates the exact configuration categories, which directly matches the surfaces enum values. It also explicitly distinguishes this read-only inspection tool from mutation or reporting siblings.

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 read-only inspection intent is implied by 'Inspect' and 'never sends or deletes,' but there is no explicit when-to-use guidance or comparison to sibling tools such as pinterest_run_report or pinterest_get_delivery_metrics. An agent must infer when this tool is the right choice rather than being told.

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