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

No annotations are provided, so the description must carry the burden. It states the primary effect: 'stops processing all active schedules'. However, it omits additional behavioral details such as reversibility, idempotency, side effects on already-scheduled items, or whether permissions are required. The description is adequate but not rich.

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 description is a single, front-loaded sentence with no filler. It efficiently conveys the action and its scope, earning a high score for conciseness and structure.

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 simple one-parameter pause operation, the description covers the essential behavior. No output schema exists, and the description does not mention return values or error conditions, but given the low complexity and the clear core behavior, it is reasonably complete. A 5 would require more context about reversibility or next steps.

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%, but there is only one parameter 'id' (string), which is clearly the campaign identifier from the tool name and description ('this campaign'). The description does not explicitly document the parameter, but the single self-explanatory parameter makes it minimally sufficient. It adds little beyond the schema.

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 uses a strong verb ('Pause') with a specific resource ('a campaign') and clearly defines the scope: 'stops processing all active schedules for this campaign'. This distinguishes it from siblings like resume_campaign and delete_campaign.

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?

The description clearly implies the context: use when you need to temporarily halt schedule processing without deleting the campaign. However, it does not explicitly mention alternatives or exclusions (e.g., 'use resume_campaign to restart', 'use delete_campaign to delete entirely'), so it stops short of a 5.

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