Discounts: create campaign

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

Discloses that it's a draft, no money charged, and returns dispatches and offers. Annotations indicate not read-only and not destructive, which aligns. Adds context beyond annotations about the two-step process and return values.

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?

Front-loaded with key purpose, each sentence is informative. Slightly dense but no wasted words, appropriately concise for the complexity.

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?

Explains return values (dispatches, offers), mentions prerequisite check (available), and outlines the next step (multi_confirm). For a beta tool with no output schema, it provides sufficient context.

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 coverage is 100% with descriptions for all three parameters. Description does not add additional meaning to parameters beyond what schema provides, meeting baseline.

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 it creates a draft campaign for listings, using specific verbs like 'Creates a draft...' and distinguishes from sibling tools by noting it's the first step, with multi_confirm for confirmation and available for eligibility checks.

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?

Explicitly tells when to use (first step, no money charged) and what to do next (confirm via multi_confirm, check eligibility via available). Provides clear sequential workflow.

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