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

The annotations already declare read-only, idempotent and non-destructive, but the description adds genuine context beyond them: synchronous execution, task support forbidden, that the payload is internal orchestration state, and explicit presentation constraints (use assistantSummary, don't dump raw JSON, mention IDs only for follow-up). Those output-handling rules are useful behavioral guidance the annotations do not cover.

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 purpose is front-loaded, but the first sentence merely repeats the title, and the bulk of the text is a generic presentation-style block that is long and reused-looking. It is readable but carries noticeable redundancy and a trailing run of imperative style rules.

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?

An output schema exists so return values needn't be explained, and annotations cover the safety profile, but this is a 16-parameter tool with 0% schema coverage and the description supplies no parameter or routing context. Small hints about output contents ('stage, terminal state, retry metadata') help, yet the agent is left guessing most inputs.

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% across 16 parameters and the description says nothing about any of them, not even the two required identifiers (advertiserId, runId). The lone word 'exact' does not convey enough to compensate for such a large undocumented parameter surface.

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 opener states a specific verb and resource plus the content of the read ('stage, terminal state and retry metadata'), so the agent knows what it fetches. However, it is essentially the title repeated verbatim and never distinguishes this from close siblings such as get_task, get_creative_intelligence, or leanriq_get_creative_intelligence_run.

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 gives instructions for how to present the response (use assistantSummary, avoid raw JSON) but no guidance on when to select this tool over alternatives like get_task or get_creative_intelligence. There is no when-to-use or when-not-to-use framing and no prerequisites or alternatives named.

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