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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known, but the description adds almost nothing on top: it does not say what stopping actually does to in-flight or queued deliveries, whether the change is reversible, or which permission is required. The word "continuous" hints at an ongoing background job, which is the only extra context offered for a destructive mutation.

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?

A single front-loaded sentence with no wasted wording. It is efficient, though the brevity shades into under-specification rather than tightness.

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 destructive toggle on a persistent sync with two undocumented parameters and no output schema, the description omits the essentials: the boolean polarity, whether stopping is reversible, and what state the destination is left in. Annotations cover the risk flag but not the operational consequences an agent needs before invoking it.

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% for both parameters, so the description is the only place semantics could be supplied — and neither sync_id nor keepSending is mentioned. Critically, the description's "starts or stops" never maps the boolean to which value means start versus stop, leaving the agent to guess that keepSending=true means continue.

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 verb pair ("starts or stops") and a specific resource ("continuous sending to a destination"), so an agent knows this is a toggle on an existing sync. It does not differentiate itself from siblings such as send_to_destination or create_destination_sync, which a reader must infer from name alone.

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 call this versus the sibling alternatives: nothing says whether an existing sync is required, whether this pauses or permanently cancels delivery, or when an agent should prefer create_destination_sync/send_to_destination instead. Usage is only implied by the verb.

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