pause_connection

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

With no annotations provided, the description carries the full burden. It discloses key behavioral outcomes: the connection will not sync until resumed and the default response is a compact confirmation. It stops short of detailing side effects on in-flight syncs or required permissions, but covers the essential behavior for a simple state-changing 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?

Two precise sentences with no filler. The first sentence states the intended action, the second explains the consequence and response behavior. Every word earns its place.

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 two-parameter tool with no output schema, the description fully covers what the tool does, its effect, and how to get more detail. It is complete and appropriate for the tool's complexity, especially among sibling tools with obvious opposites.

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 100%, so the baseline is 3. The description's note about compact confirmation and verbose=true essentially repeats the schema's verbose description, adding no new parameter-level meaning beyond what the schema already provides.

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 specific verb ('Pause') and identifies the exact resource ('a connection's sync schedule'), making the tool's purpose unmistakable. It also distinguishes itself from sibling tools like resume_connection and trigger_sync by stating the effect of the pause.

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 when to use the tool: to pause a connection's sync schedule. It also hints at the opposite operation ('until resumed') but doesn't explicitly name resume_connection as the alternative. The verbose flag instruction adds usage context but no formal exclusions or when-not-to-use guidance.

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