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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully adds that results are cursor-paginated and filterable, but says nothing about auth scopes, rate limits, or default page size behavior beyond what the schema states.

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 sentences plus an endpoint note, front-loaded with purpose before capabilities. The 'Keap: GET /campaigns' line is borderline redundant but plausible as documentation mapping, so sizing is close to optimal.

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 read-only list tool with full schema coverage and no output schema, the description covers purpose and pagination, which is the main behavioral concern. It could note the shape of the returned list (campaigns plus next_page_token), but nothing critical is missing.

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 100%, so all four parameters (filter, order_by, page_size, page_token) are already documented with examples. The description only restates these capabilities at a high level, adding no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('List marketing campaigns') and immediately disambiguates the domain term with '(automation sequences)'. Among siblings like keap_list_contacts, keap_list_tags, and keap_list_tasks, the resource is unambiguous.

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?

It states supported capabilities (filtering, ordering, cursor pagination), which implies how to drive the tool, but gives no explicit when-to-use, prerequisites, or alternatives (e.g., a get-by-id sibling). Usage is inferable rather than guided.

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