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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only vaguely states that authorization and validation match other interfaces, without specifying required permissions, create-vs-update semantics, validation rules, side effects, or idempotency behavior for a mutation tool.

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?

The text is short, but its brevity comes from omission rather than efficient structure. It is front-loaded with the tool name and a vague compatibility statement, leaving the agent with no actionable information.

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 mutation tool with no annotations, no output schema, 8 parameters, and 0% schema description coverage, the description is completely inadequate. It omits what is saved, required inputs, update semantics, validation behavior, and any lifecycle 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 description coverage is 0% across 8 parameters, including 5 required fields, and the description adds no parameter meaning whatsoever. It does not explain id, revision, lineId, contactIds, budgetCentavos, or any other field.

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 essentially restates the tool name as 'SAGOT campaigns.save' and never says what saving a campaign actually does, such as creating or updating it. It does not distinguish this tool from siblings like campaigns_start, campaigns_pause, or campaigns_preview, so the purpose remains tautological.

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 use campaigns_save versus campaigns_start, campaigns_resume, campaigns_cancel, or other campaign lifecycle tools. The note about matching authorization and validation on other surfaces does not tell an agent when this operation is appropriate.

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