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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds material context beyond them: open sessions are cancelled, a linked comment trigger is paused as a side effect, and flow.paused is fired. These are exactly the consequences an agent needs before invoking a mutation with cascading effects.

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?

Four short sentences, front-loaded with the verb and resource and then the consequences; almost every clause earns its place. The closing 'Send {} as the body' is the one line that may mislead rather than help, given the schema requires an id.

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 one-parameter destructive mutation with no output schema, the definition covers consequences, side effects and the emitted event. The only residual gap is clarity about request shape, where the empty-body instruction and the required id path are not reconciled.

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?

With a single documented parameter at 100% schema coverage, the schema already carries meaning for id, so no compensation is required. The description adds a body-format instruction ('Send {} as the body'), which is useful operational detail, though it reads slightly oddly against a required id in the schema and could prompt confusion about where id belongs.

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 and resource ('Pause a flow') and immediately qualifies what pausing means here, which separates it from adjacent siblings such as delete_flow, update_flow and activate_flow. The description also names the emitted event (flow.paused), giving an agent a concrete behavioral signature to reason about.

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 effect of pausing is described, from which an agent can infer that pause is the reversible alternative to delete_flow, but no explicit when-to-use or when-not-to-use statement is made. There is no mention of the inverse operation (activate_flow) for resuming, so routing to the correct sibling is left implicit.

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