List VWO draft campaigns

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

The description adds that drafts are non-live and non-impactful, which complements the readOnlyHint annotation. But it does not describe the response format or other behaviors like paging.

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 with no fluff. Front-loaded with the core action, followed by a clarifying statement.

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?

Given a simple list operation with readOnlyHint and openWorldHint annotations, the description provides basic context. However, it omits output details and paging behavior, which the schema partially covers.

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?

All four parameters have full schema descriptions (100% coverage). The description adds no extra parameter details, so baseline 3 applies.

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 clearly states the tool lists unpublished draft campaigns, distinguishing it from sibling tools like vwo_list_campaigns (for all campaigns) and vwo_get_draft (for a specific draft).

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 description explains drafts are not live and affect no visitors, implying when to use this tool. However, it does not explicitly exclude usage scenarios or mention alternatives.

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