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

The description supplies the underlying endpoint (GET /v1/campaigns), which mirrors structured data rather than adding behavioral context. With readOnlyHint already covering the safety profile, the description should add things like pagination behavior, result caps, or rate limits, none of which appear.

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 short, front-loaded sentences with no filler; the scope statement leads and the endpoint reference follows. Nothing needs to be trimmed for an agent to act on it.

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 trivial zero-param read tool this is close to adequate, but with no output schema the description does not indicate what a campaign record contains or whether results are paginated. A brief note on return shape would make it complete.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify beyond the already-complete empty 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 all campaigns in the workspace"), which is unambiguously distinct from the singular customerio_get_campaign. It does not, however, explicitly differentiate itself from sibling list/get tools such as customerio_get_campaign_metrics, so it stops short of a 5.

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 guidance on when to choose this over customerio_get_campaign (single campaign) or customerio_get_campaign_metrics. The scope word "all" hints at bulk retrieval, but no condition, prerequisite, or exclusion is stated.

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