campaigns_list

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'List outbound campaigns,' which indicates a read-only operation but fails to disclose pagination (max_results), ordering, side effects, or permissions. This is minimal but not entirely absent.

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 description is a single, concise sentence with no filler or redundancy. It is efficiently short, though its brevity sacrifices detail that would help in other dimensions.

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 are covered. However, the description gives no context about the domain of outbound campaigns, how to distinguish this listing from other sibling operations, or any prerequisites. For a tool with no annotations and an incomplete parameter story, the context is lacking.

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 does not mention either parameter. While the parameter names are somewhat self-explanatory, the description adds no meaning about how max_results behaves or what connect_instance_id refers to. This leaves the agent without semantic guidance beyond the raw 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?

The description uses a specific verb 'List' and a specific resource 'outbound campaigns,' which clearly differentiates it from sibling tools like campaigns_create, campaigns_describe, and campaigns_get_state. This is a concrete, non-tautological statement of the tool's function.

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 verb 'List' implies this tool is for enumerating outbound campaigns, establishing a basic usage context. However, it does not explicitly mention when to use it over alternatives like campaigns_describe or campaigns_get_state, nor does it state any exclusions. The guidance is purely implicit.

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