Get VWO campaign details

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

Annotations (readOnlyHint) already declare safe read. Description adds that it returns type, status, URLs, goals, variations, and targeting, which goes beyond annotations. Adequate behavioral context given annotations.

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?

Single sentence, front-loaded with key information ('Get the full configuration of one campaign'). No wasted words. Efficient and clear.

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 get tool with annotations and complete schema descriptions, the description is sufficient. It covers the main purpose and data returned. Could add typical usage context but not required.

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 baseline is 3. The tool description does not add parameter details, but param descriptions in schema are already rich. No additional value needed.

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?

Clearly states 'Get the full configuration of one campaign' with specific data points (type, status, URLs, goals, variations, targeting). Distinguishes from siblings like vwo_list_campaigns (list) and vwo_get_campaign_share_link (share link).

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?

No explicit when-to-use or alternatives in the description. While param descriptions hint at prerequisite calls (e.g., vwo_list_campaigns), the tool description itself lacks usage guidelines.

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