pause_bot

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

With no annotations, the description carries the full burden. It states the main effect — 'automations stop replying to this contact' — and the positivity constraint on `minutes`. It does not mention reversibility or repeated-call behavior, but the core mutation is disclosed.

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?

One concise sentence plus a short behavioral note; no filler. The action, scope, and constraints are all front-loaded.

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 2-parameter tool with no output schema and no annotations, it says enough: what it does, what each parameter means, and the observable result. It could add a mention of resume_bot for a fully round-tripped picture, but nothing essential is missing.

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. It clarifies that `minutes` must be positive and that `user_ns` should come from `find_contact`, adding meaning beyond the raw 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 specific verb ('Pause') with a clear resource ('the bot'), scopes it to one contact, and bakes in the key parameter `minutes`. This cleanly separates it from sibling tools like resume_bot and send_text.

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?

Tells the agent exactly when to use it: to pause a bot for a single contact with a positive number of minutes. It also tells where `user_ns` comes from (`find_contact`), though it doesn't explicitly name resume_bot as the reversal alternative.

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