Update Campaign

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

Discloses return format ({message, updated_fields[], campaign}) and error if campaign_id not found. IdempotentHint in annotations is consistent; description adds partial update behavior and return details.

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 concise sentences plus a one-phrase tip. No wasted words; front-loaded with purpose.

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?

Covers patch semantics, error handling, return format, and alternative tool usage. Lacks mention of total_budget parameter, but otherwise sufficient for agent decision-making.

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?

Description enumerates key updatable fields (name, status, daily_budget, bidding_strategy, end_date) beyond the schema's 14% coverage. However, the parameter total_budget is omitted from the description, slightly reducing completeness.

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?

Description clearly states 'Patch-update an existing campaign' with specific verb and resource. Distinguishes from sibling tool campaign_pause_resume by advising its use for batch status changes.

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?

Provides explicit guidance: include campaign_id from campaign_list or campaign_create, pass any subset of fields, omitted fields unchanged. Explicitly prefers campaign_pause_resume for batch status changes.

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