Continue GitHub Copilot session

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

The description reveals behavioral traits beyond annotations: it resumes the exact session ID, falls back to the newest on-disk session, and re-applies permission flags each call. This adds value over the annotations (readOnlyHint=false, openWorldHint=true) which do not specify these details. No contradiction.

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?

The description is concise with two short paragraphs. The first sentence immediately states the core purpose. The second paragraph adds crucial differentiation without redundancy. Every sentence provides value, and the information is 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?

Given the tool has an output schema and high schema coverage, the description covers all necessary context: session resumption, workspace fallback, permission behavior, and comparison to codex_continue. It is complete for an AI agent to understand when and how to use the tool correctly.

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 baseline is 3. The description adds no extra parameter details beyond the schema, but it does reinforce that 'sandbox' takes effect here, which is already in the schema. The parameter meaning is well-covered by schema descriptions themselves, so no need for more.

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 clearly states the tool continues a GitHub Copilot session rooted at a workspace, resuming its session ID. It distinguishes itself from siblings like codex_continue by mentioning permission re-application. The title 'Continue GitHub Copilot session' further clarifies the purpose.

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 explains when to use this tool: after a copilot_ask, and when you want sandbox permissions to take effect. It contrasts with codex_continue, but does not explicitly list scenarios where alternatives like antigravity_continue are preferred. The fallback behavior after restart is noted, providing context.

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