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

Annotations already declare destructiveHint=true, idempotentHint=true and non-readOnly, so the safety profile is covered. The description adds valuable grain beyond that: what actually gets suppressed (new drafts and cold emails), what is deliberately left alone (existing conversations), and that an in-flight batch is not canceled — all non-obvious side-effect scoping.

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 sentences, no filler, and the primary effect is front-loaded before the exception clauses. Every clause carries information about behavior an agent would otherwise have to guess.

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 two-parameter boolean toggle with no output schema, the description plus annotations are nearly sufficient. The remaining gap is the unaddressed relationship to resume_sending, which an agent would need before choosing between them.

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 both parameters are fully documented in structured form (enabled: true to send/false to stop; workspaceId points at get_status). The prose adds no additional parameter meaning, so the baseline of 3 applies.

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?

States a specific action (stops or restarts) on a specific resource (new outreach for one site), which is genuinely clearer than the title alone. It does not, however, distinguish itself from the sibling resume_sending, which appears to cover the same 'turn it back on' half of this tool's job.

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 defines the operational scope of the off state (no new drafts, no new cold emails) and explicitly what it does not affect, which helps an agent reason about when toggling is appropriate. But it never routes the agent between this tool and the obvious alternative resume_sending, nor states prerequisites beyond the schema-level hint to call get_status for a workspaceId.

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