Api campaigns cascade info retrieve

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds only that the result is a "preview" of cascade effects, with no detail on what is returned, whether the cascade is destructive, or how deep it goes; with annotations covering safety, this is a thin addition.

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 words with no filler, but this is under-specification rather than conciseness. A usable definition needs at least a full clause describing the operation and its target.

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?

No output schema, no parameter docs, and a two-word description leave an agent unable to determine what a "cascade preview" for a campaign returns or how to interpret the id. Given a mutating-adjacent domain object and zero schema help, the description is inadequate.

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 single required parameter `id` has 0% schema description coverage, and the description says nothing about what the id identifies or what form it takes. With low coverage the description must compensate, and it does not.

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?

"Cascade preview:" is essentially a restatement of the name/title fragment ("cascade info retrieve") rather than a description of an operation. It hints that the tool reveals cascading effects for something, but never states the verb, the resource, or what the preview contains.

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 statement of when to use this tool, when not to, or how it differs from sibling campaign tools such as campaigns_retrieve or campaigns_object_retrieve. The word "preview" faintly implies a read-only inspection step, but nothing tells an agent when to prefer it.

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