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

No annotations are provided, so the description carries the full burden and it discloses almost nothing: no pagination/limit behavior, no result ordering, no statement of what happens when app_adam_id is omitted (the schema hints at a default app). The interesting param, notification_message, implies a fallback-reply mechanism but its behavior is never explained in the description.

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 short sentence with the resource front-loaded, so nothing is buried. It is arguably too terse rather than padded, and the trailing "(CM API find)" is low-value jargon that does not earn 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?

With no annotations, no output schema, and all three parameters optional, the description should explain default scope (all campaigns for the default app?) and return shape, but it does neither. An agent cannot tell whether an empty call lists everything or errors.

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 coverage is 100%, so each parameter already carries its own description, establishing a baseline of 3. The description mentions "for an app", loosely mapping to app_adam_id, but adds no semantics for campaign_list_query or the unusual notification_message parameter beyond what the schema says.

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?

"List campaigns for an app" states a clear verb and resource, so the core operation is unambiguous. However, with siblings like get_campaign, list_campaign_reports and get_filter_sets in the set, it does not say how this list differs from a single get or from the report listing. The parenthetical "CM API find" is backend jargon that adds little for an agent.

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 versus get_campaign, list_campaign_reports, or get_filter_sets. No prerequisites (auth, session) or exclusions are mentioned, so the agent must infer routing from sibling names alone.

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