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

With no annotations, the description carries the full burden of behavioral disclosure and provides none. A pause is a state-changing, potentially reversible operation; the description says nothing about reversibility, authentication requirements beyond 'same as website/API/CLI', side effects on in-flight calls, or rate limits.

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?

Only one sentence, and it is front-loaded with a tautological identifier rather than the essential information. It is under-specified, not concise — the brevity removes needed content rather than waste.

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 two required parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It provides no return behavior, no preconditions, and no error cases.

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%, so the description must compensate, but it adds no meaning for 'id' or 'workspaceId' beyond the schema's UUID format. It does not clarify that 'id' is the campaign ID or what happens if the campaign is not in a pausable state.

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 names the tool via 'campaigns.pause' but never states in plain language what it does — pause a running campaign — nor what state change results. It is essentially a restatement of the name plus a note about authorization, which is a tautology rather than a purpose statement.

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 guidance on when to use this versus the numerous sibling tools like campaigns_cancel, campaigns_resume, campaigns_start, or agents_pause. The agent must infer that 'pause' is distinct from 'cancel', which is a critical distinction the description omits.

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