copilot_pause_thread

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful side effect not in structured data: 'Pause cancels unsent drafts', which tells the agent this call has a consequential downstream effect on draft content.

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 short sentences, no filler, and the secondary but important side-effect warning is placed immediately after the core action. Every sentence carries information.

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 three-required-parameter mutation with no output schema, the description covers the action and the draft side effect but leaves the revision-conflict outcome, post-call state, and threadId semantics implicit. Annotations carry the safety profile, so the remaining gaps are moderate rather than severe.

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 'revision' as an expected/optimistic-concurrency value and implies 'paused' is the pause/resume switch, but 'threadId' gets no explanation and the mismatch behavior is unstated.

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 and resource ('Pause/resume a thread') with the added qualifier 'at its expected revision'. It's clear what the tool does, but it never distinguishes itself from nearby siblings like copilot_delete_thread or copilot_release_manual_override, so an agent has to infer when this is the right copilot mutation.

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?

There is no explicit guidance on when to pause vs. resume, when not to call it, or what to do if the thread is already in the desired state. The 'expected revision' phrase implies a concurrency check but the description doesn't say how to obtain the revision or what happens on a mismatch.

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